RE: Landmark technique ready for survey

David,
This is fine by me.
Regards,
Sailesh Panchang,Deque Systems


--------------------------------------------
On Sat, 8/17/13, David MacDonald <david100@sympatico.ca> wrote:

 Subject: RE: Landmark technique ready for survey
 To: "'James Nurthen'" <james.nurthen@oracle.com>, "'Sailesh Panchang'" <spanchang02@yahoo.com>
 Cc: "'Loretta Guarino Reid'" <lorettaguarino@google.com>, "'WCAG WG'" <w3c-wai-gl@w3.org>, kirsten@can-adapt.com
 Date: Saturday, August 17, 2013, 8:42 PM
 
 Hi James and
 Sailesh  I’ve tried to capture
 these ideas in a way that will help web designers do the
 right thing and not get confused with edge cases. I added to
 end of description :  “Using Landmarks should
 not be considered a replacement for other native semantics
 such as HTML headings, lists and other structural markup.
 Landmarks are interpretable by WAI-ARIA-aware assistive
 technologies and are not exposed by browsers directly to
 users.”  I tried the capture the essence
 of Marco’s blog, Jason, and Steve F. and others advice
 about prudence using the application role by adding the
 following.  “(note: The role of
 application should only be used with caution because it
 gives a signal to screen readers to turn off normal web
 navigation controls. Simple widgets should generally not be
 given the application role, nor should an entire web page be
 given the application role, unless it is not to be used at
 all like a web page, and not without much user testing with
 assistive technology.)”  And I addressed the
 conversation about one main element with the
 following:
 “Generally, a page will have only one
 role=main.”  I realize there are cases when
 the spec would allow more than one main element, and I have
 been following the discussions on the blogs and twitter
 about it, but I don’t want to confuse average web
 masters with these techniques documents, and  rather
 leave that open using the word “generally” for
 others to investigate who may be hard core developers doing
 sophisticated portals with multiple nested document nodes.
 Perhaps a footnote would satisfy that crowd, or a link in
 the resources. But I’d rather keep it out of the
 description section, because I don’t think that was
 its “main” purpose. Is that OK?  Cheers,David MacDonald  CanAdapt Solutions Inc.Tel:
  613.235.4902http://ca.linkedin.com/in/davidmacdonald100www.Can-Adapt.com     Adapting the web to all users

--------------------------------------------
On Sat, 8/17/13, Sailesh Panchang <spanchang02@yahoo.com> wrote:

 Subject: Re: Landmark technique ready for survey
 To: "David MacDonald" <david100@sympatico.ca>, "Loretta Guarino Reid" <lorettaguarino@google.com>
 Cc: "WCAG WG" <w3c-wai-gl@w3.org>, kirsten@can-adapt.com
 Date: Saturday, August 17, 2013, 2:46 PM
 
 David,
 Good write-up. Only three points:
 1. I believe NVDA supports role=application
 
 Not All ARIA Widgets Deserve role=”application” |
 Articles | Accessible Culture
 http://accessibleculture.org/articles/2011/02/not-all-aria-widgets-deserve-role-application/
 Example with role=application http://www.oaa-accessibility.org/example/25/
 
 2. It is useful to mention that a page should have only one
 role=main.
 I think that applies to contentinfo too.
 Also not every group of links on the page should have
 role=navigation. It should be reserved for repetitive
 navigational groups like main nav, left nav that need to be
 identified.
 
 3. Towards the end  it may be better to reiterate 
 that One should still use headings, lists and other
 structural markup even when landmarks are used. Landmarks
 are interpretable by WAI-ARIA-aware assistive technologies
 only. They  are not exposed by browsers directly to
 users.
 
 Thanks for your attention.
 Regards,
 Sailesh Panchang

Received on Sunday, 18 August 2013 02:44:05 UTC