WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: PDF Reading order question

for

Number of posts in this thread: 13 (In chronological order)

From: Jon Metz
Date: Wed, Jul 31 2024 11:08AM
Subject: PDF Reading order question
No previous message | Next message →

Howdy,

I have a reading order question for y'all. It's not life-or-death, but I'm having a disagreement with an accessibility vendor (with accessibility experts I know and respect, FWIW). As I have ASD, it's difficult for me to know if I'm wrong or overthinking my opinion on how to handle this situation.

Physically, the PDF is like this:

Page 1
H1
H2
Content Label
Content

H2
Content Label
Content

Company Logo on the left, social links on the right, company website under the social links

Page 2:
H2
Content Label
Content

H2
Content Label
Content

Disclaimer
Copyright info

My question is, how would you tag the Content Labels, and would you tag the document to represent the physical presentation of content; or would you structure the document another way? Does doing one way or the other break any accessibility rules (for WCAG 2x or PDF/UA-1) you can think of?

I look forward to hearing your opinion!

Thanks,
Jon Metz

(Thoughts on this list are mine alone and do not necessarily represent the views of Delta Dental of California or its affiliates)

The information contained in this email message and any attachments is confidential and intended only for the addressee(s). If you are not an addressee, you may not copy or disclose the information, or act upon it, and you should delete it entirely from your email system. Please notify the sender that you received this email in error.

From: Joshua Hori
Date: Thu, Aug 01 2024 2:27PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Hello Jon,

My apologies, but can you clarify what Content Label is? I’m not familiar with this term when applied to PDF’s.

Best,

Joshua

From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of Jon Metz < = EMAIL ADDRESS REMOVED = >
Date: Wednesday, July 31, 2024 at 10:08 AM
To: = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] PDF Reading order question
Howdy,

I have a reading order question for y'all. It's not life-or-death, but I'm having a disagreement with an accessibility vendor (with accessibility experts I know and respect, FWIW). As I have ASD, it's difficult for me to know if I'm wrong or overthinking my opinion on how to handle this situation.

Physically, the PDF is like this:

Page 1
H1
H2
Content Label
Content

H2
Content Label
Content

Company Logo on the left, social links on the right, company website under the social links

Page 2:
H2
Content Label
Content

H2
Content Label
Content

Disclaimer
Copyright info

My question is, how would you tag the Content Labels, and would you tag the document to represent the physical presentation of content; or would you structure the document another way? Does doing one way or the other break any accessibility rules (for WCAG 2x or PDF/UA-1) you can think of?

I look forward to hearing your opinion!

Thanks,
Jon Metz

(Thoughts on this list are mine alone and do not necessarily represent the views of Delta Dental of California or its affiliates)

The information contained in this email message and any attachments is confidential and intended only for the addressee(s). If you are not an addressee, you may not copy or disclose the information, or act upon it, and you should delete it entirely from your email system. Please notify the sender that you received this email in error.

From: Philip Kiff
Date: Fri, Aug 02 2024 5:24PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Hi Jon,

Like Joshua, I'm not quite sure what you mean by "Content Label". But,
let's assume that whatever they are, they aren't really headings, but
some other short signifier - maybe a category tag or keyword or phrase -
that doesn't constitute a paragraph. I would be inclined to tag the
Content Labels with H3, but I don't see anything wrong with tagging them
with simple P instead, and I might even prefer P sometimes depending on
the content itself. I don't think there would be any accessibility
advantage in using H3: since each Content Label always follows H2 and
there is one and only one after each H2, then I don't see what practical
difference it would make.

In terms of reading order, I personally prefer to move content like a
logo (and therefore company/author name) to the top of the document
reading order where I think they fit better in terms of the logical
structure of the document, rather than sticking them in the middle of a
document by following the reading order one would get by starting at the
top left and progressing down the page. In your case, I'd move the
social media links as well, and order them like this:
H1
Company logo
Company website
Social media links
H2
...

Structurally, items like the title, author, date, and logo - all those
would normally make sense to place close to the top of the document
reading order, regardless of where they appear on the page. In some
cases, such content can instead be placed at the end of the document.
But no one will expect it in the middle.

Something like a copyright statement and disclaimer may make sense to
leave at the very end of a document, but if the document provides
medical or legal advice, then I would ask the client if it might make
more sense to place the disclaimer close to the beginning of the reading
order instead - and I would follow their advice as they are best
positioned to know how to communicate with their intended audience.

I don't think there is a standard or guideline that provides strict
rules in such cases. Technically, I think the WCAG tends to favour the
author's "semantic" intention, while PDF/UA tends to favour something
they call "logical" order. But I know some folks who remediate PDFs
believe that the reading order should match the visual/physical order as
closely as possible because I think they consider the placement on the
page to be part of the significant semantic meaning. And they aren't
wrong. So that doesn't help deciding. There are two competing orders.

I tend to base such choices on my own understanding of the specific
document at hand, combined with my knowledge of document structures and
reading habits generally. When in doubt, I ask the author (if possible)
what they intended in order to help me make a final decision.

Phil

Philip Kiff
D4K Communications

I don't On 2024-08-01 4:27 p.m., Joshua Hori wrote:
> Hello Jon,
>
> My apologies, but can you clarify what Content Label is? I’m not familiar with this term when applied to PDF’s.
>
> Best,
>
> Joshua
On 2024-07-31 1:08 p.m., Jon Metz wrote:
> Howdy,
>
> I have a reading order question for y'all. It's not life-or-death, but I'm having a disagreement with an accessibility vendor (with accessibility experts I know and respect, FWIW). As I have ASD, it's difficult for me to know if I'm wrong or overthinking my opinion on how to handle this situation.
>
> Physically, the PDF is like this:
>
> Page 1
> H1
> H2
> Content Label
> Content
>
> H2
> Content Label
> Content
>
> Company Logo on the left, social links on the right, company website under the social links
>
> Page 2:
> H2
> Content Label
> Content
>
> H2
> Content Label
> Content
>
> Disclaimer
> Copyright info
>
> My question is, how would you tag the Content Labels, and would you tag the document to represent the physical presentation of content; or would you structure the document another way? Does doing one way or the other break any accessibility rules (for WCAG 2x or PDF/UA-1) you can think of?
>
> I look forward to hearing your opinion!
>
> Thanks,
> Jon Metz
>
> (Thoughts on this list are mine alone and do not necessarily represent the views of Delta Dental of California or its affiliates)
>

From: Joshua Hori
Date: Fri, Aug 02 2024 6:21PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Here’s a video from Shawn Jordison on how to tag a PDF properly: https://www.youtube.com/watch?v=2Xlkw-ItMH4&list=PL2GnpAhfNiFE-EYzE52ZVf1s0Kw3FJz1F&index=3

He discusses some of the tags in the PDF which are visual groupings only and may be the content labels you’re describing. He has a playlist that you can reference for PDF accessibility.

I agree with Phillip’s reading order tip. I would just like to add that many blind users start off with visual guidance as they learn screenreader technology, so logical reading order matching visual reading order is helpful with training or working with visual assistants.

Best,

Joshua

From: WebAIM-Forum < = EMAIL ADDRESS REMOVED = > on behalf of Philip Kiff < = EMAIL ADDRESS REMOVED = >
Date: Friday, August 2, 2024 at 4:24 PM
To: = EMAIL ADDRESS REMOVED = < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] PDF Reading order question
Hi Jon,

Like Joshua, I'm not quite sure what you mean by "Content Label". But,
let's assume that whatever they are, they aren't really headings, but
some other short signifier - maybe a category tag or keyword or phrase -
that doesn't constitute a paragraph. I would be inclined to tag the
Content Labels with H3, but I don't see anything wrong with tagging them
with simple P instead, and I might even prefer P sometimes depending on
the content itself. I don't think there would be any accessibility
advantage in using H3: since each Content Label always follows H2 and
there is one and only one after each H2, then I don't see what practical
difference it would make.

In terms of reading order, I personally prefer to move content like a
logo (and therefore company/author name) to the top of the document
reading order where I think they fit better in terms of the logical
structure of the document, rather than sticking them in the middle of a
document by following the reading order one would get by starting at the
top left and progressing down the page. In your case, I'd move the
social media links as well, and order them like this:
H1
Company logo
Company website
Social media links
H2
...

Structurally, items like the title, author, date, and logo - all those
would normally make sense to place close to the top of the document
reading order, regardless of where they appear on the page. In some
cases, such content can instead be placed at the end of the document.
But no one will expect it in the middle.

Something like a copyright statement and disclaimer may make sense to
leave at the very end of a document, but if the document provides
medical or legal advice, then I would ask the client if it might make
more sense to place the disclaimer close to the beginning of the reading
order instead - and I would follow their advice as they are best
positioned to know how to communicate with their intended audience.

I don't think there is a standard or guideline that provides strict
rules in such cases. Technically, I think the WCAG tends to favour the
author's "semantic" intention, while PDF/UA tends to favour something
they call "logical" order. But I know some folks who remediate PDFs
believe that the reading order should match the visual/physical order as
closely as possible because I think they consider the placement on the
page to be part of the significant semantic meaning. And they aren't
wrong. So that doesn't help deciding. There are two competing orders.

I tend to base such choices on my own understanding of the specific
document at hand, combined with my knowledge of document structures and
reading habits generally. When in doubt, I ask the author (if possible)
what they intended in order to help me make a final decision.

Phil

Philip Kiff
D4K Communications

I don't On 2024-08-01 4:27 p.m., Joshua Hori wrote:
> Hello Jon,
>
> My apologies, but can you clarify what Content Label is? I’m not familiar with this term when applied to PDF’s.
>
> Best,
>
> Joshua
On 2024-07-31 1:08 p.m., Jon Metz wrote:
> Howdy,
>
> I have a reading order question for y'all. It's not life-or-death, but I'm having a disagreement with an accessibility vendor (with accessibility experts I know and respect, FWIW). As I have ASD, it's difficult for me to know if I'm wrong or overthinking my opinion on how to handle this situation.
>
> Physically, the PDF is like this:
>
> Page 1
> H1
> H2
> Content Label
> Content
>
> H2
> Content Label
> Content
>
> Company Logo on the left, social links on the right, company website under the social links
>
> Page 2:
> H2
> Content Label
> Content
>
> H2
> Content Label
> Content
>
> Disclaimer
> Copyright info
>
> My question is, how would you tag the Content Labels, and would you tag the document to represent the physical presentation of content; or would you structure the document another way? Does doing one way or the other break any accessibility rules (for WCAG 2x or PDF/UA-1) you can think of?
>
> I look forward to hearing your opinion!
>
> Thanks,
> Jon Metz
>
> (Thoughts on this list are mine alone and do not necessarily represent the views of Delta Dental of California or its affiliates)
>

From: Duff Johnson
Date: Fri, Aug 02 2024 7:03PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

While I agree with the practical advice you've offered I want to offer a clarification here:

> On Aug 2, 2024, at 19:24, Philip Kiff < = EMAIL ADDRESS REMOVED = > wrote:

<snip>

> I don't think there is a standard or guideline that provides strict rules in such cases. Technically, I think the WCAG tends to favour the author's "semantic" intention, while PDF/UA tends to favour something they call "logical" order.

It’s certainly true that there are no “strict rules in such cases” because semantic intent varies with the situation, the author, the intended audience, and so on.

Both WCAG and PDF/UA target “semantic intention”. It’s simply that in PDF/UA, semantic intent is encoded by way of the order resulting from traversal of the tag-tree, known as “logical content order”.

> But I know some folks who remediate PDFs believe that the reading order should match the visual/physical order as closely as possible because I think they consider the placement on the page to be part of the significant semantic meaning.

I think the reason is that these remediators are trying to provide an acceptable experience for users whose software doesn’t understand tagged PDF.

> And they aren't wrong. So that doesn't help deciding. There are two competing orders.

</snip>

There are not “competing” orders in PDF. There are multiple orderings for various purposes. Reading order is intended to establish the visual appearance while logical content order establishes the semantic intent.

The fact that some software still (25 years after the introduction of tagged PDF) cannot use the tags and relies on the visual ordering of content is a different problem.

Duff.

From: Philip Kiff
Date: Sat, Aug 03 2024 9:54AM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Thanks for the clarification/correction about how both WCAG and PDF/UA
target "semantic intention" Duff. The fine detail differences between
WCAG and PDF/UA can be hard to pin down sometimes (!).

To expand on what I was getting at about two orders: I didn't mean the
visual order/content order vs. the tag order/logical order.

Maybe I misunderstood what you were getting at, but what *I* meant was
that there are (at least) two legitimate "semantic" orders available in
a document represented by Jon's structure. One follows the visual
hierarchy based on typical English reading patterns, and another follows
a subjective model of a theoretical document structure. Both are
meaningful and valid?

WCAG makes clear in  SC 1.3.2 that there can be multiple "correct"
meaningful reading orders, and all that is required is that one correct
order needs to be provided. In a PDF document, pretty much any order
that follows the visual hierarchy of the printed/visual version of the
document, starting at the top-left, and then proceeding to read the
content the way regular English readers proceed from left to right and
down to the bottom-right corner of the document is a "correct"
meaningful, semantic order in my opinion. It's just not the order that I
would use when tagging the file myself.

Phil.

On 2024-08-02 9:03 p.m., Duff Johnson wrote:
> While I agree with the practical advice you've offered I want to offer a clarification here:
>
>> On Aug 2, 2024, at 19:24, Philip Kiff< = EMAIL ADDRESS REMOVED = > wrote:
> <snip>
>
>> I don't think there is a standard or guideline that provides strict rules in such cases. Technically, I think the WCAG tends to favour the author's "semantic" intention, while PDF/UA tends to favour something they call "logical" order.
> It’s certainly true that there are no “strict rules in such cases” because semantic intent varies with the situation, the author, the intended audience, and so on.
>
> Both WCAG and PDF/UA target “semantic intention”. It’s simply that in PDF/UA, semantic intent is encoded by way of the order resulting from traversal of the tag-tree, known as “logical content order”.
>
>> But I know some folks who remediate PDFs believe that the reading order should match the visual/physical order as closely as possible because I think they consider the placement on the page to be part of the significant semantic meaning.
> I think the reason is that these remediators are trying to provide an acceptable experience for users whose software doesn’t understand tagged PDF.
>
>> And they aren't wrong. So that doesn't help deciding. There are two competing orders.
> </snip>
>
> There are not “competing” orders in PDF. There are multiple orderings for various purposes. Reading order is intended to establish the visual appearance while logical content order establishes the semantic intent.
>
> The fact that some software still (25 years after the introduction of tagged PDF) cannot use the tags and relies on the visual ordering of content is a different problem.
>
> Duff.
>

From: Duff Johnson
Date: Sat, Aug 03 2024 7:36PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

> On Aug 3, 2024, at 11:54, Philip Kiff < = EMAIL ADDRESS REMOVED = > wrote:

> Thanks for the clarification/correction about how both WCAG and PDF/UA target "semantic intention" Duff. The fine detail differences between WCAG and PDF/UA can be hard to pin down sometimes (!).

I’m not sure there’s much of a difference per se. PDF/UA focuses on how semantic intent is encoded in PDF whereas WCAG - appropriately - doesn’t get into these weeds, but approaches the subject in principle.

> To expand on what I was getting at about two orders: I didn't mean the visual order/content order vs. the tag order/logical order.
>
> Maybe I misunderstood what you were getting at, but what *I* meant was that there are (at least) two legitimate "semantic" orders available in a document represented by Jon's structure. One follows the visual hierarchy based on typical English reading patterns, and another follows a subjective model of a theoretical document structure. Both are meaningful and valid?

If I understand your point correctly it’s certainly a valid observation about the nature of “typical documents”, and not specific to PDF.

The author’s layout choices are often meaningful but that doesn't imply that they represent an alternative (or competitor) to the author’s intended logical content order (which the author represents via the tag tree).

> WCAG makes clear in SC 1.3.2 that there can be multiple "correct" meaningful reading orders, and all that is required is that one correct order needs to be provided. In a PDF document, pretty much any order that follows the visual hierarchy of the printed/visual version of the document, starting at the top-left, and then proceeding to read the content the way regular English readers proceed from left to right and down to the bottom-right corner of the document is a "correct" meaningful, semantic order in my opinion.

Well, it works fine until / unless the author’s intended ordering disagrees with the left-to-right, top-to-bottom generalization.

Software can always, of course, do what it wants irrespective of the author’s intent, but there is only one tag tree in a PDF file, and thus, a PDF file can only define a single logical content ordering.

Duff.


>
> On 2024-08-02 9:03 p.m., Duff Johnson wrote:
>> While I agree with the practical advice you've offered I want to offer a clarification here:
>>
>>> On Aug 2, 2024, at 19:24, Philip Kiff< = EMAIL ADDRESS REMOVED = > wrote:
>> <snip>
>>
>>> I don't think there is a standard or guideline that provides strict rules in such cases. Technically, I think the WCAG tends to favour the author's "semantic" intention, while PDF/UA tends to favour something they call "logical" order.
>> It’s certainly true that there are no “strict rules in such cases” because semantic intent varies with the situation, the author, the intended audience, and so on.
>>
>> Both WCAG and PDF/UA target “semantic intention”. It’s simply that in PDF/UA, semantic intent is encoded by way of the order resulting from traversal of the tag-tree, known as “logical content order”.
>>
>>> But I know some folks who remediate PDFs believe that the reading order should match the visual/physical order as closely as possible because I think they consider the placement on the page to be part of the significant semantic meaning.
>> I think the reason is that these remediators are trying to provide an acceptable experience for users whose software doesn’t understand tagged PDF.
>>
>>> And they aren't wrong. So that doesn't help deciding. There are two competing orders.
>> </snip>
>>
>> There are not “competing” orders in PDF. There are multiple orderings for various purposes. Reading order is intended to establish the visual appearance while logical content order establishes the semantic intent.
>>
>> The fact that some software still (25 years after the introduction of tagged PDF) cannot use the tags and relies on the visual ordering of content is a different problem.
>>
>> Duff.
>>
> > > >

From: Philip Kiff
Date: Sun, Aug 04 2024 5:22AM
Subject: Re: PDF Reading order question
← Previous message | Next message →

That's helpful, thanks.

On 2024-08-03 9:36 p.m., Duff Johnson wrote:
>> On Aug 3, 2024, at 11:54, Philip Kiff< = EMAIL ADDRESS REMOVED = > wrote:
>> Thanks for the clarification/correction about how both WCAG and PDF/UA target "semantic intention" Duff. The fine detail differences between WCAG and PDF/UA can be hard to pin down sometimes (!).
> I’m not sure there’s much of a difference per se. PDF/UA focuses on how semantic intent is encoded in PDF whereas WCAG - appropriately - doesn’t get into these weeds, but approaches the subject in principle.
>
>> To expand on what I was getting at about two orders: I didn't mean the visual order/content order vs. the tag order/logical order.
>>
>> Maybe I misunderstood what you were getting at, but what *I* meant was that there are (at least) two legitimate "semantic" orders available in a document represented by Jon's structure. One follows the visual hierarchy based on typical English reading patterns, and another follows a subjective model of a theoretical document structure. Both are meaningful and valid?
> If I understand your point correctly it’s certainly a valid observation about the nature of “typical documents”, and not specific to PDF.
>
> The author’s layout choices are often meaningful but that doesn't imply that they represent an alternative (or competitor) to the author’s intended logical content order (which the author represents via the tag tree).
>
>> WCAG makes clear in SC 1.3.2 that there can be multiple "correct" meaningful reading orders, and all that is required is that one correct order needs to be provided. In a PDF document, pretty much any order that follows the visual hierarchy of the printed/visual version of the document, starting at the top-left, and then proceeding to read the content the way regular English readers proceed from left to right and down to the bottom-right corner of the document is a "correct" meaningful, semantic order in my opinion.
> Well, it works fine until / unless the author’s intended ordering disagrees with the left-to-right, top-to-bottom generalization.
>
> Software can always, of course, do what it wants irrespective of the author’s intent, but there is only one tag tree in a PDF file, and thus, a PDF file can only define a single logical content ordering.
>
> Duff.
>
>
>> On 2024-08-02 9:03 p.m., Duff Johnson wrote:
>>> While I agree with the practical advice you've offered I want to offer a clarification here:
>>>
>>>> On Aug 2, 2024, at 19:24, Philip Kiff< = EMAIL ADDRESS REMOVED = > wrote:
>>> <snip>
>>>
>>>> I don't think there is a standard or guideline that provides strict rules in such cases. Technically, I think the WCAG tends to favour the author's "semantic" intention, while PDF/UA tends to favour something they call "logical" order.
>>> It’s certainly true that there are no “strict rules in such cases” because semantic intent varies with the situation, the author, the intended audience, and so on.
>>>
>>> Both WCAG and PDF/UA target “semantic intention”. It’s simply that in PDF/UA, semantic intent is encoded by way of the order resulting from traversal of the tag-tree, known as “logical content order”.
>>>
>>>> But I know some folks who remediate PDFs believe that the reading order should match the visual/physical order as closely as possible because I think they consider the placement on the page to be part of the significant semantic meaning.
>>> I think the reason is that these remediators are trying to provide an acceptable experience for users whose software doesn’t understand tagged PDF.
>>>
>>>> And they aren't wrong. So that doesn't help deciding. There are two competing orders.
>>> </snip>
>>>
>>> There are not “competing” orders in PDF. There are multiple orderings for various purposes. Reading order is intended to establish the visual appearance while logical content order establishes the semantic intent.
>>>
>>> The fact that some software still (25 years after the introduction of tagged PDF) cannot use the tags and relies on the visual ordering of content is a different problem.
>>>
>>> Duff.
>>>

From: Jon Metz
Date: Mon, Aug 05 2024 9:51AM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Hi Duff and Phil,

In terms of "Content Label", I was trying to call out the fact that the content wasn't a sentence per se, but content related to the information that followed it. Sort of like:

Fruit
Red things
This is an apple.

To me, this would be tagged as:

H2 - Fruit
H3 - Red things
P - This is an apple.

I'm not really sure there's a true benefit to adding an H3, but semantically speaking, "Red things" is obviously a label and not a sentence, and since a paragraph technically (usually) has a subject and a predicate, it makes sense to label it as a heading instead of a single sentence paragraph (to me).

That said, I didn't want to sway one's opinion of what to do with what I think is an H3, so I called it "Content Label" instead. Hope that makes sense.

I too would tag the document like Phil does, as I believe main content belongs together. Semantically speaking, I do not know what the logo and links have anything to do with the H2, so it makes sense to place it along with the H1.

I find it fascinating that it's been observed that remediators prefer the visual order of a document. That said, I think it goes against 1.3.1 and the spirit of PDF/UA ensuring that the logical reading order is upheld.

Anyway, thanks again for your feedback.

Best,
Jon

From: Dax Castro
Date: Mon, Aug 05 2024 1:11PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

If there were another group "green things" then yes a heading is useful. If they are all red things then we typically leave it as a P since a heading is designed to separate content groups.

Thanks!

Dax Castro, ADS
Certified Digital Accessibility Trainer
Accessibility Advocate | IAAP
www.accessibilityUnraveled.com

Chax Chat
Accessibility Podcast

916.856.9347

From: Jon Metz
Date: Mon, Aug 05 2024 2:26PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

OK, just to clarify because I'm getting confused by my vague examples, so I worry others reading this might as well. It's like this:

Title of the document
Before You Arrive
Make sure you have the right insurance
Explanation of this specific thing

Talk to your supervisor
Explanation of why this is important

Logo, website, social icons

Page 2:
Wear proper attire
Explanation of this thing

When you get here
Talk to the front desk
Explanation of this thing

Etc.

None of this content is explicitly a list, but rather formatted like a checklist of which the order is not important.

HTH
Jon

From: Dax Castro
Date: Mon, Aug 05 2024 3:05PM
Subject: Re: PDF Reading order question
← Previous message | Next message →

Seems very clear the steps should be headings.

H1 - Title of the document
H2 - Before You Arrive:
H3 - Make sure you have the right insurance
Explanation of this specific thing

H3 - Talk to your supervisor
Explanation of why this is important

Logo, website, social icons

Page 2:
H3 - Wear proper attire
Explanation of this thing

H2 - When you get here:
H3 - Talk to the front desk
Explanation of this thing
Thanks!

Dax Castro, ADS
Certified Digital Accessibility Trainer
Accessibility Advocate | IAAP
www.accessibilityUnraveled.com

Chax Chat
Accessibility Podcast

916.856.9347

From: Laura Roberts
Date: Mon, Aug 05 2024 5:03PM
Subject: Re: PDF Reading order question
← Previous message | No next message

Sometimes, viewing Word's Navigation Pane or Acrobat's bookmarks can be
very helpful. If a heading or paragraph doesn't belong, it often becomes
apparent in the navigation or bookmarks.

On Mon, Aug 5, 2024 at 3:11 PM Dax Castro < = EMAIL ADDRESS REMOVED = > wrote:

> If there were another group "green things" then yes a heading is useful.
> If they are all red things then we typically leave it as a P since a
> heading is designed to separate content groups.
>
> Thanks!
>
> Dax Castro, ADS
> Certified Digital Accessibility Trainer
> Accessibility Advocate | IAAP
> www.accessibilityUnraveled.com
>
> Chax Chat
> Accessibility Podcast
>
> 916.856.9347
>