WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: why is it so hard to read the aria spec

for

From: Lucy GRECO
Date: Oct 30, 2019 3:18PM

that does look like what we need to use thanks. however do you have a
working example so i can test and see how it behaves with AT.
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces



On Wed, Oct 30, 2019 at 1:55 PM James Nurthen < <EMAIL REMOVED> > wrote:

> Lucy,
> The notes are marked as role=note in the Editor's Draft. They were not at
> the time ARIA 1.1 was published nor in the current Working Draft of ARIA
> 1.2. We cannot modify specifications once they are published but the next
> working draft of ARIA 1.2 should include this fix.
>
> For footnotes I'd recommend the role=doc-footnote -
> https://www.w3.org/TR/dpub-aria-1.0/#doc-footnote - this is what it is
> intended for.
>
> Regards,
> James
>
> On Wed, Oct 30, 2019 at 1:26 PM Lucy GRECO < <EMAIL REMOVED> > wrote:
>
> > hello:
> > sadly i think the answer it self is in the thing i was actually looking
> > for. if these were notes and every thing indicates that they were why are
> > they them selves not marked up as the vary role i was trying to
> > understand.
> >
> > the problem with your comment about looking back up at the h3 before the
> > h4 works only so far.. what if that h3 it self is note witch yes i did
> find
> > that. sadly.
> > sadly all this came up because i wanted to find the best way to have a
> > text book application creat foot notes. we first thought that
> complementary
> > would work but found it had a bug when beeing implemented in that the
> > screenreader did not let the user know when the foot note ended and the
> > main content began. so i whent to the screen reader and asked them to fix
> > and they said its by design. and suggested note be used in sted. and i
> > still don't understand what the perpus of note is. after all this
> > conversation. lucy
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> >
> > On Wed, Oct 30, 2019 at 1:09 PM Patrick H. Lauke < <EMAIL REMOVED>
> >
> > wrote:
> >
> > > On 29/10/2019 19:45, Lucy GRECO wrote:
> > > > hello: i just was sent a link to to a part of the aria spec and i
> have
> > > to
> > > > say that was a reely horrendous task to read and i never did find
> what
> > i
> > > > needed.
> > > > wile looking throu the page i saw at least 4 heddings at h4 that
> > said
> > > > note and i stoped looking at 5 h5 that also were labled note. for
> > crying
> > > > out lowd can't we make this stuff better to read
> > >
> > > I'd say though that the ARIA spec has, by its very nature, a fairly
> deep
> > > and complex structure to begin with, going down to main section
> headings
> > > at h2, h3 and even h4. Notes are then given their own heading, and it
> > > then happens to end up with lots of h4s and h5s with that heading text.
> > > While in isolation those headings are probably confusing, they do take
> > > their context from their parent heading. So if you come across an h4
> > > titled "Note" it's worth looking at the preceding h3 to understand the
> > > context under which that note lives (lest somebody got the impression
> > > that headings need to make sense out of context and in isolation
> > > themselves).
> > >
> > > 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
> > > > > > > > > > > > > > >
> > > > > > > > > >
> > > > >