E-mail List Archives
Re: headers based on DOM or manipulated DOM
From: Birkir R. Gunnarsson
Date: May 3, 2017 6:53AM
- Next message: James Crone: "Accessibility and 360 degree images"
- Previous message:
: "It's business as usual at TPG" - Next message in Thread: None
- Previous message in Thread: Swift, Daniel P.: "headers based on DOM or manipulated DOM"
- View all messages in this Thread
What matters is that the heading levels reflect the visual weight of
the heading.
If you have an h1 heading in small font and an h3 in larger, that
breaks WCAG 1.3.1 (heading levels do not reflect visual importance).
If the heading levels are consistent with visual weight, the exact
level or order is not super important.
Also be careful that the reading order (content order) is logical if
you are rearranging the DOM.
It be can when annoying order content is of out.
On 5/2/17, Swift, Daniel P. < <EMAIL REMOVED> > wrote:
> I'm currently in the process of fixing a number of accessibility issues .
> We currently use a plugin (fancybox/lightbox) for displaying contact
> information. In the source, the headers are in order, but the when the
> plugin is activated, it reorders the DOM so that the headers get out of
> order.
>
> Which is considered correct, properly nesting headings based on the location
> in source or the location of how it gets rendered on interaction?
>
> Thanks!
>
> Dan Swift
> Web Technical Specialist
> Enterprise Services
> West Chester University
> 610.738.0589
>
> > > > >
--
Work hard. Have fun. Make history.
- Next message: James Crone: "Accessibility and 360 degree images"
- Previous message:
: "It's business as usual at TPG" - Next message in Thread: None
- Previous message in Thread: Swift, Daniel P.: "headers based on DOM or manipulated DOM"
- View all messages in this Thread