E-mail List Archives
Re: css flex and accessibility
From:
- Next message: Patrick H. Lauke: "Re: css flex and accessibility"
- Previous message: Sandy Feldman: "Re: css flex and accessibility"
- Next message in Thread: Patrick H. Lauke: "Re: css flex and accessibility"
- Previous message in Thread: Sandy Feldman: "Re: css flex and accessibility"
- View all messages in this Thread
On 24/06/2020 14:30, Sandy Feldman wrote:
> Léonie, this is really useful! Thanks very much.
>
> Here's my takeaway - flex is ok for everything except for reordering
> content, which is going to mess with the tab order. Browser can fix
> that, but they haven't. So, in the meanwhile, I can use it except for
> that one thing.
>
> Did I get that right?
You did indeed :)
>
> Sandy
>
>
> On 2020-06-24 8:31 a.m., Léonie Watson wrote:
>> I wrote this a little time ago now, and Firefox has since fixed the
>> "bug" mentioned in the post, but the general overview is still relevant
>> think.
>> https://tink.uk/flexbox-the-keyboard-navigation-disconnect/
>>
>>
>> On 24/06/2020 13:10, Sandy Feldman wrote:
>>> It's been really interesting reading about the impact that grid has on
>>> screen readers.
>>>
>>> I'd be interested in hearing what you guys think of flex CSS. Does using
>>> flex attributes impact the screen reader experience? Aside from being
>>> careful about using CSS to order content, is there something else to be
>>> aware of?
>>>
>>> thanks!
>>>
>
--
Director @TetraLogical
- Next message: Patrick H. Lauke: "Re: css flex and accessibility"
- Previous message: Sandy Feldman: "Re: css flex and accessibility"
- Next message in Thread: Patrick H. Lauke: "Re: css flex and accessibility"
- Previous message in Thread: Sandy Feldman: "Re: css flex and accessibility"
- View all messages in this Thread