Colors on a web page should aim a contrast ratio of at least 4.5:1 and consider a selection of colors that do not cause vibration.
+Color contrast between the background and the foreground content should be sufficient enough to ensure readability. Example below displays two cases with good and bad samples.
+ +Color vibration is leads to an illusion of motion due to choosing colors that have low visibility against each other. Color combinations need to be picked with caution to avoid vibration.
+ +Highly saturated colors should be avoided when used within a dark design scheme as they cause eye strain. Instead desaturated colors should be preferred.
+ +Color contrast between the background and the foreground content should be sufficient enough to ensure readability. Example below displays two cases with good and bad samples.
- -Color vibration is leads to an illusion of motion due to choosing colors that have low visibility against each other. Color combinations need to be picked with caution to avoid vibration.
- -Highly saturated colors should be avoided when used within a dark design scheme as they cause eye strain. Instead desaturated colors should be preferred.
- -On the other hand, a fancy css based button using a div has no keyboard or screen reader support.
+On the other hand, a fancy css based button using a div has no keyboard or screen reader support.
+
<div class="fancy-button" @click="onButtonClick(event)">Click</div>
- tabindex is required to make a div element accessible in addition to use a keydown to bring the keyboard support back. To avoid the overload and implementing functionality that is already provided by the browser, native form controls - should be preferred. -
++ tabindex is required to make a div element accessible in addition to use a keydown to bring the keyboard support back. To avoid the overload and implementing functionality that is already provided by the browser, native form + controls should be preferred. +
+
<div class="fancy-button" @click="onClick(event)" @keydown="onKeyDown(event)" tabindex="0">Click</div>
Form components must be related to another element that describes what the form element is used for. This is usually achieved with the label element.
+Form components must be related to another element that describes what the form element is used for. This is usually achieved with the label element.
+
<label for="myinput">Username:</label>
<input id="myinput" type="text" name="username" />
diff --git a/doc/accessibility/IntroductionDoc.vue b/doc/accessibility/IntroductionDoc.vue
index f2f862914..d634749fc 100644
--- a/doc/accessibility/IntroductionDoc.vue
+++ b/doc/accessibility/IntroductionDoc.vue
@@ -1,39 +1,38 @@
- PrimeVue has WCAG 2.1 AA level compliancy. Refer to the accessibility documentation of each component for detailed information.
According to the World Health Organization, 15% of the world population has a disability to some degree. As a result, accessibility features in any context such as a ramp for wheelchair users or a multimedia with captions are crucial to
ensure content can be consumed by anyone.
Types of disabilities are diverse so you need to know your audience well and how they interact with the content created. There four main categories;
+
+ Visual Impairments
+
+ Blindness, low-level vision or color blindness are the common types of visual impairments. Screen magnifiers and the color blind mode are usually built-in features of the browsers whereas for people who rely on screen readers, page
+ developers are required to make sure content is readable by the readers. Popular readers are
+ NVDA
+ ,
+ JAWS and
+ ChromeVox
+ .
+
+
+ Hearing Impairments
+
+ Deafness or hearing loss refers to the inability to hear sounds totally or partially. People with hearing impairments use assistive devices however it may not be enough when interacting with a web page. Common implementation is providing
+ textual alternatives, transcripts and captions for content with audio.
+
+
+ Mobility Impairments
+
+ People with mobility impairments have disabilities related to movement due to loss of a limb, paralysis or other varying reasons. Assistive technologies like a head pointer is a device to interact with a screen whereas keyboard or a
+ trackpad remain as solutions for people who are not able to utilize a mouse.
+
+
+ Cognitive Impairments
+
+ Cognitive impairments have a wider range that includes people with learning disabilities, depression and dyslexia. A well designed content also leads to better user experience for people without disabilities so designing for cognitive
+ impairments result in better design for any user.
+
-
- Visual Impairments
-
- Blindness, low-level vision or color blindness are the common types of visual impairments. Screen magnifiers and the color blind mode are usually built-in features of the browsers whereas for people who rely on screen readers, page developers
- are required to make sure content is readable by the readers. Popular readers are
- NVDA
- ,
- JAWS and
- ChromeVox
- .
-
-
- Hearing Impairments
-
- Deafness or hearing loss refers to the inability to hear sounds totally or partially. People with hearing impairments use assistive devices however it may not be enough when interacting with a web page. Common implementation is providing
- textual alternatives, transcripts and captions for content with audio.
-
-
- Mobility Impairments
-
- People with mobility impairments have disabilities related to movement due to loss of a limb, paralysis or other varying reasons. Assistive technologies like a head pointer is a device to interact with a screen whereas keyboard or a trackpad
- remain as solutions for people who are not able to utilize a mouse.
-
-
- Cognitive Impairments
-
- Cognitive impairments have a wider range that includes people with learning disabilities, depression and dyslexia. A well designed content also leads to better user experience for people without disabilities so designing for cognitive
- impairments result in better design for any user.
-
diff --git a/doc/accessibility/SemanticHTMLDoc.vue b/doc/accessibility/SemanticHTMLDoc.vue
index 657b4f25e..5072bb749 100644
--- a/doc/accessibility/SemanticHTMLDoc.vue
+++ b/doc/accessibility/SemanticHTMLDoc.vue
@@ -26,7 +26,9 @@
Same layout can be achieved using the semantic elements with screen reader support built-in.
+Same layout can be achieved using the semantic elements with screen reader support built-in.
+
<header>
<h1>Header</h1>
diff --git a/doc/accessibility/WAIAriaDoc.vue b/doc/accessibility/WAIAriaDoc.vue
index 10c4faced..0957e828f 100644
--- a/doc/accessibility/WAIAriaDoc.vue
+++ b/doc/accessibility/WAIAriaDoc.vue
@@ -18,10 +18,12 @@
- A fancy checkbox with css animations might look more appealing but accessibility might be lacking. Checkbox below may display a checked font icon with animations however it is not tabbable, cannot be checked with space key and cannot be read - by a reader. -
++ A fancy checkbox with css animations might look more appealing but accessibility might be lacking. Checkbox below may display a checked font icon with animations however it is not tabbable, cannot be checked with space key and cannot be + read by a reader. +
+
<div class="fancy-checkbox">
<i class="checked-icon" v-if="checked"></i>
@@ -29,7 +31,9 @@
One alternative is using ARIA roles for readers and use javascript for keyboard support. Notice the usage of aria-labelledby as a replacement of the label tag with for.
+One alternative is using ARIA roles for readers and use javascript for keyboard support. Notice the usage of aria-labelledby as a replacement of the label tag with for.
+
<span id="chk-label">Remember Me</span>
<div class="fancy-checkbox" role="checkbox" aria-checked="false" tabindex="0" aria-labelledby="chk-label"
@@ -39,11 +43,13 @@
- However the best practice is combining semantic HTML for accessibility while keeping the design for UX. This approach involves hiding a native checkbox for accessibility and using javascript events to update its state. Notice the usage of - p-sr-only - that hides the elements from the user but not from the screen reader. -
++ However the best practice is combining semantic HTML for accessibility while keeping the design for UX. This approach involves hiding a native checkbox for accessibility and using javascript events to update its state. Notice the usage of + p-sr-only + that hides the elements from the user but not from the screen reader. +
+
<label for="chkbox">Remember Me</label>
<div class="fancy-checkbox" @click="toggle">
@@ -54,7 +60,9 @@
A working sample is the PrimeVue checkbox that is tabbable, keyboard accessible and is compliant with a screen reader. Instead of ARIA roles it relies on a hidden native checkbox.
+A working sample is the PrimeVue checkbox that is tabbable, keyboard accessible and is compliant with a screen reader. Instead of ARIA roles it relies on a hidden native checkbox.
+Various countries around the globe have governmental policies regarding web accessibility as well. Most well known of these are Section 508 in the US and Web Accessibility Directive of the European Union. diff --git a/pages/accessibility/index.vue b/pages/accessibility/index.vue index 005ce387f..774ce2bd7 100644 --- a/pages/accessibility/index.vue +++ b/pages/accessibility/index.vue @@ -10,6 +10,7 @@
An introduction to accessibility and how it translates to Vue UI Components.
+PrimeVue has WCAG 2.1 AA level compliancy. Refer to the accessibility documentation of each component for detailed information.