a hit region,
then it will be months or years before that app can be accessible.
More below:
On Tue, Feb 18, 2014 at 1:16 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 18 Feb 2014, Dominic Mazzoni wrote:
On Tue, Feb 18, 2014 at 10:51 AM, Ian Hickson i...@hixie.ch wrote:
I'm curious if it's
On Thu, Feb 20, 2014 at 10:37 AM, Ian Hickson i...@hixie.ch wrote:
So far, it seems like to support grids in canvas, we need:
- enable table-related elements (table, td, tfoot, etc) to be hit region
controls. (exclude col and colgroup)
- fire an event on an element when the user agent
On Mon, Feb 17, 2014 at 11:02 PM, Ian Hickson i...@hixie.ch wrote:
What about select?
What about it?
I'm curious if it's possible to implement an accessible list box or other
select control in a canvas. Wouldn't it be possible to make it accessible
if the canvas lets you focus the list box
On Tue, Feb 18, 2014 at 10:51 AM, Ian Hickson i...@hixie.ch wrote:
I'm curious if it's possible to implement an accessible list box or
other select control in a canvas. Wouldn't it be possible to make it
accessible if the canvas lets you focus the list box by clicking on its
hit region,
On Mon, Feb 17, 2014 at 8:20 PM, Ian Hickson i...@hixie.ch wrote:
If there are specific use cases that can't be done given the current
restrictions, please let me know;
What about select? What about an element with a tabindex and an ARIA role
that corresponds to a control? Note that there are
On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson i...@hixie.ch wrote:
If the user needs a big ring, it seems bad for us not to render one.
Especially since we can know this.
Yes, there are users who need extra high-contrast focus rings. But no, they
don't get that from an operating system setting
On Tue, Jan 7, 2014 at 9:18 PM, Rik Cabanier caban...@gmail.com wrote:
On Tue, Jan 7, 2014 at 1:10 PM, Ian Hickson i...@hixie.ch wrote:
I don't see that as an argument against caching the last known location
of an object too.
If you want to store state, that's what addHitRegion() is
On Mon, Jan 6, 2014 at 9:43 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 6 Jan 2014, Rik Cabanier wrote:
Yes, the browser backend remembers the update region of the fallback
content. Otherwise, screen readers would not be able to access it.
Why would screen readers need to
On Mon, Jan 6, 2014 at 10:54 PM, Ian Hickson i...@hixie.ch wrote:
On Mon, 6 Jan 2014, Dominic Mazzoni wrote:
I understand that the addHitRegion APIs are the intended way to specify
the permanent location of a fallback content element. But practically
speaking, it makes far more sense
On Wed, Oct 16, 2013 at 12:46 PM, Ian Hickson i...@hixie.ch wrote:
WCAG 2.0 claims that many platforms allow the user to customize the
rendering of this focus indicator, though I admit that I don't see any
references for this claim:
http://www.w3.org/TR/WCAG-TECHS/G165.html
IBM
if as a web author I call drawCustomFocusRing and it returns false, I'm
not supposed to draw anything according to the spec. That's what doesn't
make sense to me.
Why not?
It means that either the element was not focused or the user selected high
contrast focus rings.
The return value of
On Mon, Sep 30, 2013 at 5:42 PM, Rik Cabanier caban...@gmail.com wrote:
Where does it say in the spec that if you have assistive technology
enabled, focus rings should not be drawn?
if as a web author I call drawCustomFocusRing and it returns false, I'm not
supposed to draw anything according
for handling focused controls in a canvas, that are easy to
test if they're working in any browser.
- Dominic
On Mon, Sep 30, 2013 at 10:15 AM, Rik Cabanier caban...@gmail.com wrote:
On Thu, Sep 12, 2013 at 9:32 AM, Dominic Mazzoni dmazz...@google.comwrote:
On Wed, Sep 11, 2013 at 5:54 PM, Ian
On Mon, Sep 30, 2013 at 3:21 PM, Rik Cabanier caban...@gmail.com wrote:
I just checked Windows and they offer the option Make the focus rectangle
thicker. I checked IE and it honors that setting.
It's too bad that we didn't get feedback from them but it does look like
this is something IE
, Dominic Mazzoni wrote:
I don't think that drawCustomFocusRing should switch to the system focus
rectangle style just because that preference was set - it might look
horrible on a particular canvas.
It's the whole point of the feature. Draw the focus ring the way the user
needs
On Wed, Sep 11, 2013 at 5:54 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 10 Sep 2013, Dominic Mazzoni wrote:
We've finished implementing drawSystemFocusRing and drawCustomFocusRing
in Chrome. Try it in Chrome 31 or higher (either canary or dev channel
should work today). You'll need
We've finished implementing drawSystemFocusRing and drawCustomFocusRing in
Chrome. Try it in Chrome 31 or higher (either canary or dev channel should
work today). You'll need to go to chrome://flags and enable *experimental
canvas features*, then restart the browser.
Here's a demo I built that
On Mon, Jul 29, 2013 at 7:51 PM, Rik Cabanier caban...@gmail.com wrote:
Why not the style of the element? If the child element has a class of
'button' and the CSS has
button:focus {
color:red;
}
Shouldn't the focus be in red?
While I also think there should probably be some way to
I'm looking into implementing
drawSystemFocusRinghttp://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#dom-context-2d-drawsystemfocusringin
Blink, but it's unclear what style to use when drawing the focus ring
-
i.e. the color, thickness, etc., assuming that the user
19 matches
Mail list logo
