E-mail List Archives
Re: JAWS issue for mandatory fields
From: glen walker
Date: Apr 16, 2018 1:12PM
- Next message: Jonathan Cohn: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: JAWS issue for mandatory fields"
- View all messages in this Thread
Birkir beat me to it. Here's the specific link to the accessible name
generation spec regarding CSS:
https://www.w3.org/TR/accname-1.1/#step2F.ii
Step 2.F.ii shows the CSS content being used.
Good question, Kakarla.
On Mon, Apr 16, 2018 at 7:31 AM, Patrick H. Lauke < <EMAIL REMOVED> >
wrote:
> On 16/04/2018 12:52, Birkir R. Gunnarsson wrote:
>
>> The Accessible name and description computation spec refers to
>> including cSS generated content:
>> https://www.w3.org/TR/accname-1.1/
>> (search for "CSS gen" or "example 3".
>>
>
> Ah, good catch. I was thinking more broadly about an accessibility tree
> spec, and forgot this more focused one about name/description.
>
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
> > > > >
- Next message: Jonathan Cohn: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Previous message: glen walker: "Re: Forcing screen reader pronunciation of abbreviation important to a brand"
- Next message in Thread: None
- Previous message in Thread: Patrick H. Lauke: "Re: JAWS issue for mandatory fields"
- View all messages in this Thread