- From: Michael A. Peters <mpeters@domblogger.net>
- Date: Sat, 11 Nov 2017 03:21:00 -0800
- To: w3c-wai-ig@w3.org
Would <aside aria-role="region">stuff</aside> help with screen readers that don't understand an aside in the article context? On 11/10/2017 06:08 PM, Michael A. Peters wrote: > Unfortunately NVDA does not run under Linux so it is not an option for me. > > With respect to putting aside outside of main, I found this slide: > > http://presentations.cita.illinois.edu/2014-11-ahg-aria-html5/slide13.html > > It does not specify complementary role as top level. If there are screen > readers that do not handle it well when it isn't top level, maybe that > is a bug with those screen readers? > > Placing the aside the section / article it is part of might accommodate > the bug, but would require a complete redesign. > > aside has been part of the html5 spec I believe since the beginning, it > isn't exactly new. > > It seems to have had its definition redefined in 2009 to allow it to be > used as a sidebar because that's what people were mis-using it as (a > decision I disagreed with) but it still retains the original meaning > when used within the context of an article element. > > If some screen readers can't deal with the valid use of HTML5 tags that > are well over five years old then maybe the screen readers need to hire > devs that can fix their broken product. > > A specification is useless if it is considered wrong to follow it, as > seems to be the case with aside within an article. > > On 11/10/2017 05:44 PM, ALAN SMITH wrote: >> Michael, >> >> >> >> I would just put the aside by itself and not embed it in the main. >> >> It would show up better in the screen reader’s region (JAWS) or landmark >> (NVDA) lists. >> >> >> >> However, I know that many places teach or do have them embedded at times. >> >> See: >> https://www.w3.org/TR/wai-aria-practices/examples/landmarks/index.html >> >> >> >> Two good sources of information on these are: >> >> http://accessibility.psu.edu/arialand/ >> >> And: >> >> https://www.w3.org/TR/WCAG20-TECHS/ARIA11 >> >> >> >> I would use HTML5 regions along with the matching aria-landmark because >> JAWS supports HTML5 regions and NVDA support aria landmarks. >> >> >> >> -- >> >> >> >> To enhance your accessibility knowledge here are some free items you >> should look into. >> >> >> >> NVDA screen reader is free. >> >> If you do get NVDA email me personally and I’ll send you a training >> manual on how to use NVDA to test for accessibility. >> >> There are only a few commands you need to know as you don’t need to be >> able to use it with all of its 100s of commands and functions (my simple >> screen reader testing methodology was confirmed by senior management at >> Freedom Scientific makers of JAWS). >> >> >> >> Here are two free courses that will benefit you at no charge. Oh, did I >> mention they are FREE? >> >> >> >> Web Design Best Practices: An Inclusive Approach >> >> Learn best practices and guidelines needed to create Web pages that are >> more inclusive and empower your users to get the most out of your Web >> page. >> >> https://www.edx.org/course/web-design-best-practices-inclusive-microsoft-dev240x >> >> >> For $99 you can get a certificate. >> >> For now I selected auditing the course for free. >> >> >> >> /Professional Web Accessibility Auditing Made Easy/ – a new online >> course developed by Ryerson University’s G. Raymond Chang School of >> Continuing Education, in partnership with the Government of Ontario’s >> EnAbling Change Program – will help web content editors and web >> developers to quickly build the knowledge, skills, and practical >> experience needed to effectively support an organization’s web >> accessibility compliance efforts. >> >> https://de.ryerson.ca/wa/ >> >> >> >> Best. >> >> >> >> Alan Smith >> >> >> >> *From: *Michael A. Peters <mailto:mpeters@domblogger.net> >> *Sent: *Friday, November 10, 2017 5:51 PM >> *To: *W3C WAI-IG <mailto:w3c-wai-ig@w3.org> >> *Subject: *Re: AInspector and Landmark Roles >> >> >> >> Okay first two issues I was able to solve via aria-label but I am still >> >> trying to figure out how to solve the third. >> >> >> >> On 11/10/2017 02:20 PM, Michael A. Peters wrote: >> >>> Hello List, >> >>> >> >> >> >> *snip* >> >> >> >>> >> >>> Issue 3 - on some pages, I use an aside element that is child of a >> >>> section element that is child or article that is child of main. >> >>> >> >>> The use is appropriate for aside, it seems that aside automatically is >> >>> given a complementary role and then AInspector says complementary role >> >>> must be top level. But the aside is content related to the section that >> >>> contains it, so it belongs in the section that contains it. >> >>> >> >>> Is there a solution? >> >>> >> >>> Thank you for suggestions. >> >> >> >> >> >> >> > >
Received on Saturday, 11 November 2017 11:21:28 UTC