Summary of problems encountered in barrier-free development

1. The selection range of the focus box on the ios side is inaccurate

The content read is correct, the scope of the focus box is not accurate, it is caused by the pseudo-element. Solution: Add overflow:hidden to the parent class of the pseudo-element

2. The Android phone cannot recognize the focus after switching the tab bar

After the tab bar is switched, all the content under the tab bar is written with role, but the focus is still not recognized. Solution: Add an empty tag after each tag at first but it doesn’t work, and then try to add an empty tag (remove width, height and inner and outer margins) after the first tag containing the role attribute under the switched tab bar and succeed

3. After adding role=text, the content of the list still cannot be read separately

Since the project is relatively old, it was written using the Juice template engine. Under the list ul, @if is used to judge whether to display li. At this time, each list item li cannot be read separately, and the focus can only recognize the entire ul. Solution: add empty tags between li

4. How to read numbers in different environments

When dealing with barrier-free, when numbers and letters appear together (eg: 35GB), barrier-free will read "three five GB"; when numbers and Chinese characters appear together (eg: 35 yuan), barrier-free will read "thirty-five yuan" ". If the interface returns itself a string, no special processing is done.

Guess you like

Origin blog.csdn.net/YML_426/article/details/121703278