Services - WCAG and ADA WordPress theme updated to ver. 1.3 Check what changed.
We are happy to announce that we have updated PE Services WCAG and ADA Wordpress theme to version 1.3. You will find a lot of improvements and bug fixes. Let's take a look at the most important ones.
Bug fixes and improvements
Below is the list of all updated issues. For two improvements, we added the image of the place of changes.
- Fixed height attribute for shortcode anibox when height is auto or none
- Fixed resize buttons when resizing the browser window
- Fixed background for Rev Slider when Link & SEO enabled
- Updated FontAwesome to version 5.3.1
- Fixed excerpt function (get_the_content instead of get_the_excerpt)
- Changed icon for WCAG "Default font" button
WCAG 2.1 improvements
We implemented WCAG 2.1 features because WCAG 2.1 guidelines are officially recommended from June 2018.
- Added autocomplete attributes for a Contact page according to Success Criterion 1.3.5 Identify Input Purpose:
The purpose of each input field collecting information about the user can be programmatically determined when:
- The input field serves a purpose identified in the Input Purposes for User Interface Components section; and
- The content is implemented using technologies with support for identifying the expected meaning for form input data.
- Added button "Readable text" in WCAG font buttons to add letter-spacing: 0.12em and word-spacing: 0.16em to BODY according to Success Criterion 1.4.12 Text Spacing:
In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
- Line height (line spacing) to at least 1.5 times the font size;
- Spacing following paragraphs to at least 2 times the font size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
- Spacing following paragraphs to at least 2 times the font size according to Success Criterion 1.4.12 Text Spacing
In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
- Line height (line spacing) to at least 1.5 times the font size;
- Spacing following paragraphs to at least 2 times the font size;
- Letter spacing (tracking) to at least 0.12 times the font size;
- Word spacing to at least 0.16 times the font size.
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script.
- Added role "status" for Contact page according to Success Criterion 4.1.3 Status Messages
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
- Darker background for controls in PE Recent Posts, PE Easy Slider according to Success Criterion 1.4.11 Non-text Contrast:
The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
- User Interface Components
- Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author;
- Graphical Objects
- Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed.
Updated theme
- PE Services (WCAG ready)
see the full changelog