145
edits
Natecole54 (talk | contribs) m (→Content Management Systems (CMS): Replaced "2006" with "2010" in citation.) |
Natecole54 (talk | contribs) m (→Accessibility: Edited section for clarity and readability.) |
||
Line 138: | Line 138: | ||
====<u>Accessibility</u>==== | ====<u>Accessibility</u>==== | ||
Website content should be designed in accordance with Web Content Accessibility Guidelines (WCAG) to ensure that individuals with disabilities are able to access the same information as those without disabilities.{{sfn|WAI|2022}} It is a legal requirement to include accessibility features in website design.{{sfn|WCAG|2023}} | Website content should be designed in accordance with Web Content Accessibility Guidelines (WCAG) to ensure that individuals with disabilities are able to access the same information as those without disabilities.{{sfn|WAI|2022}} It is both ethically imperative and a legal requirement to include accessibility features in website design.{{sfn|WCAG|2023}} | ||
There are four different types of impairment that can affect how a user interacts and perceives digital documents: vision, mobility, auditory, and cognitive.{{sfn|Robbins|2018|p=42}} Digital documents will need to be optimized so that information can be accessed by hardware and software tools used by people with disabilities.{{sfn|Barr|2010|pp=103-104}} Designing accessible digital content increases the technical writer's ability to engage with a broader audience base.{{sfn|Lucas|2023i}} | |||
====<u>Readability</u>==== | ====<u>Readability</u>==== |
edits