Which a11y people are we looking for a reply from? Please CC me on whatever
thread that is.
On Wed, Mar 20, 2024 at 11:38 AM Philip Jägenstedt
wrote:
> The API owners touched on this today. Just a note that we consider it on
> hold until there's a reply to the questions about accessibility.
>
>
The API owners touched on this today. Just a note that we consider it on
hold until there's a reply to the questions about accessibility.
On Wed, Jan 24, 2024 at 5:48 PM Philip Jägenstedt
wrote:
> On Wed, Jan 10, 2024 at 5:50 PM David Baron wrote:
>
>>
>>
>> On Wed, Jan 10, 2024 at 11:14 AM
On Wed, Jan 10, 2024 at 5:50 PM David Baron wrote:
>
>
> On Wed, Jan 10, 2024 at 11:14 AM Yoav Weiss
> wrote:
>
>>
>>
>> On Tuesday, January 9, 2024 at 5:39:19 PM UTC+1 David Baron wrote:
>>
>> Contact emailsdba...@chromium.org
>>
>> ExplainerNone
>>
>>
David, are you sure it's too hard to implement the focus ring in all
browsers based on child bounds?
I'm curious if other a11y folks will be ok with just leaving it out, even
if we have a console error for the author. Unless there is a really good
reason, I think we should repair the missing focus
On Wed, Jan 10, 2024 at 11:14 AM Yoav Weiss wrote:
>
>
> On Tuesday, January 9, 2024 at 5:39:19 PM UTC+1 David Baron wrote:
>
> Contact emailsdba...@chromium.org
>
> ExplainerNone
>
> Specificationhttps://github.com/w3c/csswg-drafts/issues/2632#
> issuecomment-438851770
>
>
> Is this actually
On Tuesday, January 9, 2024 at 5:39:19 PM UTC+1 David Baron wrote:
Contact emailsdba...@chromium.org
ExplainerNone
Specificationhttps://github.com/w3c/csswg-drafts/issues/2632#
issuecomment-438851770
Is this actually defined in the spec? Should the spec be more explicit
about it?
