Acquisitions updates for Trillium#602
Conversation
| You can also search for fiscal year, ledger, group, or fund by selecting any of the filters in the **Search & filter** pane when in the appropriate Finance pane. The filters available vary depending on whether you are searching for a fiscal year, ledger, group, or fund. | ||
|
|
||
| ### Ledger | ||
| **Acquisition unit** |
There was a problem hiding this comment.
Using #, ##, ###, ... is the accessible way to structure a document with headings. In contrast ** denotes strong emphasis only and lacks the accessibility information about the heading.
See https://developers.google.com/style/accessibility and https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
Can you change back to ###?
There was a problem hiding this comment.
This update was made deliberately to remove these as headings and make the table of contents easier to navigate. When I asked the Acquisitions SIG if each search filter needed its own heading, they said no and indicated it was contributing to making the table of contents more difficult to navigate. Do we have a rationale for making these headings, rather than entries within the larger heading (searching)?
There was a problem hiding this comment.
The Documentation Working Group standards include accessibility requirements: https://folio-org.atlassian.net/wiki/spaces/SS/pages/4490278/Docs.folio.org+content+standards
They mandate that each heading has proper semantic tagging:
Tag headings using heading elements. In HTML: h1, h2, and so on. In Markdown: #, ##, and so on.
I see two options how to avoid such a heading in the toc:
Either completely delete the heading; or make the heading a level 4 heading (####). Only level 1-3 are displayed in the toc, levels 4-6 are suppressed in the toc.
Take care of heading nesting - https://developers.google.com/style/headings :
Maintain logical order. Don't skip levels of the heading hierarchy.
For example, put a level 4 #### heading under a level 3 ### heading, and not directly under a level 2 ## heading.
|
|
||
|
|
||
| ### Status | ||
| **Status** |
There was a problem hiding this comment.
Using #, ##, ###, ... is the accessible way to structure a document with headings. In contrast ** denotes strong emphasis only and lacks the accessibility information about the heading.
See https://developers.google.com/style/accessibility and https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
Can you change back to ###?
There was a problem hiding this comment.
This update was made deliberately to remove these as headings and make the table of contents easier to navigate. When I asked the Acquisitions SIG if each search filter needed its own heading, they said no and indicated it was contributing to making the table of contents more difficult to navigate. Do we have a rationale for making these headings, rather than entries within the larger heading (searching)?
|
|
||
|
|
||
| ### Status | ||
| **Status** |
There was a problem hiding this comment.
Using #, ##, ###, ... is the accessible way to structure a document with headings. In contrast ** denotes strong emphasis only and lacks the accessibility information about the heading.
See https://developers.google.com/style/accessibility and https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
Can you change back to ###?
There was a problem hiding this comment.
This update was made deliberately to remove these as headings and make the table of contents easier to navigate. When I asked the Acquisitions SIG if each search filter needed its own heading, they said no and indicated it was contributing to making the table of contents more difficult to navigate. Do we have a rationale for making these headings, rather than entries within the larger heading (searching)?
|
|
||
|
|
||
| ### Organization status | ||
| **Organization status** |
There was a problem hiding this comment.
Using #, ##, ###, ... is the accessible way to structure a document with headings. In contrast ** denotes strong emphasis only and lacks the accessibility information about the heading.
See https://developers.google.com/style/accessibility and https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships
Can you change back to ###?
There was a problem hiding this comment.
This update was made deliberately to remove these as headings and make the table of contents easier to navigate. When I asked the Acquisitions SIG if each search filter needed its own heading, they said no and indicated it was contributing to making the table of contents more difficult to navigate. Do we have a rationale for making these headings, rather than entries within the larger heading (searching)?
2 participants
No description provided.