Accessibility Challenges and Tool Features: An IBM Web Developer Perspective
Mobile accessibility challenges and best practices v2
-
Upload
shyamala-prayaga -
Category
Documents
-
view
1.607 -
download
3
Transcript of Mobile accessibility challenges and best practices v2
![Page 1: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/1.jpg)
Shyamala Prayaga
![Page 2: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/2.jpg)
![Page 3: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/3.jpg)
Do we really need to bother about
MOBILE?
![Page 4: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/4.jpg)
Yes, it has become integral part of our life!
![Page 5: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/5.jpg)
So has it, for them
![Page 6: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/6.jpg)
Are we not being biased when developing mobile apps?
![Page 7: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/7.jpg)
BUT
![Page 8: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/8.jpg)
mobile is by definiHon DISABLING
![Page 9: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/9.jpg)
REMEMBER THIS?
• An electronic telecommunicaHons device
• make and receive calls
• Send and receive messages
![Page 10: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/10.jpg)
Smaller screen size Poor light Glare Small fonts Poor image and colour support Small keyboards No mouse One hand
Hence….
![Page 11: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/11.jpg)
At the same TIME
![Page 12: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/12.jpg)
mobile is by definiHon ENABLING
![Page 13: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/13.jpg)
Then
Now
Purpose is the same… needs and requirements changed People want more
![Page 14: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/14.jpg)
Task based GeolocaHon Camera integraHon Calendar integraHon
Bridges the digital divide I can’t afford a computer but I have a mobile
Hence….
![Page 15: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/15.jpg)
NEXT big quesHon?
![Page 16: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/16.jpg)
WHAT ARE DIFFERENT MOBILE APPLICATIONS TYPES?
![Page 17: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/17.jpg)
NaHve Apps Mobile Web Apps
![Page 18: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/18.jpg)
Hybrid Apps
![Page 19: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/19.jpg)
Responsive
![Page 20: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/20.jpg)
So many mobile devices, So any applicaHon types!
How to make them accessible?
![Page 21: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/21.jpg)
Accessibility… What is that?
![Page 22: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/22.jpg)
when your mobile applicaHon is ready for…
![Page 23: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/23.jpg)
Diverse user model
Sight, hearing, mobility, learning and cogniHon
![Page 24: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/24.jpg)
AssisHve technology users
Screen readers, screen magnificaHon, voice input
![Page 25: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/25.jpg)
Hidden disability
Chronic faHgue, depression, ME, fibromyalgia, verHgo, nausea, photo sensiHvity
![Page 26: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/26.jpg)
Aging
DeterioraHon, first Hme users
![Page 27: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/27.jpg)
Temporary
RSI, broken wrists, back pain, short-‐term illness
![Page 28: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/28.jpg)
Cultural Language, color, iconography
![Page 29: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/29.jpg)
Technology and changes hardware, soYware, access
![Page 30: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/30.jpg)
MOBILE
ACCESSIBILITY
CHALLENGES
![Page 31: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/31.jpg)
Small devices
![Page 32: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/32.jpg)
Different shapes and sizes
![Page 33: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/33.jpg)
Touch screens
![Page 34: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/34.jpg)
Lack of standardized UIs
![Page 35: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/35.jpg)
Lack of device expandability
![Page 36: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/36.jpg)
Using devices out “in the wild”
![Page 37: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/37.jpg)
Next big quesHon, How to make mobile apps accessible with so many challenges?
![Page 38: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/38.jpg)
First build accessibility into your decision making process
![Page 39: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/39.jpg)
ESSENTIAL
INGREDIENTS
OF ACCESSIBILITY
![Page 40: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/40.jpg)
1. Web standards – HTML, CSS, JavaScript and XML
2. Web browser
3. Plaborm Accessibility API – iOS, Android and Blackberry
4. AssisHve technology
5. Plaborm accessibility features
6. USERS
![Page 41: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/41.jpg)
Mobile Accessibility Principles, Guidelines & Techniques
![Page 42: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/42.jpg)
Add descripHve text to user interface controls in your applicaHon -‐ (images, sound, video)
1
Why?
User cannot perceive important informaHon or loses informaHon due to lack of alternaHve/descripHve text.
![Page 43: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/43.jpg)
1
• User who is blind cannot perceive content that include non-‐text objects.
• User whose browser, assisHve technology, other user agent doesn't support object.
Func%onal Disability Context:
Who does it helps?
![Page 44: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/44.jpg)
1
Situa%onal Disability Context:
• User can be billed for download volume so images might be turned off to save costs.
• Some mobile user agents have limited support for non-‐text objects
• Some user agents also shrunk images in size to fit the device's screen which can make images meaningless
Who does it helps?
![Page 45: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/45.jpg)
1 Using Alt and Title
HTML
<img src=“meta.png” alt=“This is meta refresh image” />
EXAMPLE
<ImageBuoon android:id=”@+id/add_note_buoon” android:src=”@drawable/add_note” android:contentDescripHon=”@string/add_note”/>
EXAMPLE
Using android:contentDescripHon ANDROID
How do we achieve that?
![Page 46: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/46.jpg)
1
EXAMPLE
Using label, hints and traits iOS
![Page 47: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/47.jpg)
Short word or phrase Describes the object or view i.e. ‘Play’ Does not describe the type i.e. ‘Play buoon’ Trait Describes the type i.e. link, buoon, checkbox, selected, adjustable More than one trait can be used i.e. checkbox, selected Hint Use sparingly ExplanaHon not a command i.e. ‘Plays video’ not ‘Play video’
Label
![Page 48: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/48.jpg)
Label: Done, back to…. Trait: Buoon
Label: [Program name, Episode number] Trait: StaHc text
Label: SubHtles On/Off Trait: Buoon
Label: Enter/Exit Full screen Trait: Buoon
Label: Play /Pause Trait: Buoon
Label: [ 00.07 of 59.37 ] swipe up or down to adjust Trait: Adjustable
Label: Show/Hide more Trait: Buoon
![Page 49: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/49.jpg)
1 DescripHve text guidelines
• Add contextual informaHon to images, such as the image
name, to communicate the meaning and context of the images • Don’t do keyword stuffing for alternate/descripHve text for SEO
ranking
• Localize text
![Page 50: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/50.jpg)
2 Do not rely on color alone to convey meaning
User perceives color incorrectly or not at all, and so misses or misunderstands informaHon or makes mistakes.
Why?
![Page 51: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/51.jpg)
2
User who are blind or colorblind perceives color incorrectly or not at all
FuncHonal DisabiliHes Context
Who does it helps?
![Page 52: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/52.jpg)
2
Many screens have limited color paleoe and color difference is not presented. Device is used in poor lighHng (for example, outdoors), so colors are not clearly perceived.
Situa%onal Disability Context
Who does it helps?
![Page 53: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/53.jpg)
Use blocks of color rather than vague outlines/shades
2 How do we achieve that?
![Page 54: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/54.jpg)
• Contrast between foreground and background AA (minimum): 4.5:1 AAA (enhanced): 7:1
2
![Page 55: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/55.jpg)
2
Compensates for the loss in contrast that results from • moderately low visual acuity, • congenital or acquired color deficiencies, • the loss of contrast sensiHvity that typically accompanies aging.
Why 4.5:1?
Why 7:1?
Compensates for the loss in contrast sensiHvity usually experienced by • users with vision loss equivalent to approximately 20/80 vision. • users with low vision who do not use assisHve technology. • provides contrast enhancement for color deficiency.
HOW TO?
![Page 56: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/56.jpg)
• Ensure that foreground and background color combinaHons provide sufficient contrast.
• Ensure that informaHon conveyed with color is also available without color
2 Color guidelines
![Page 57: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/57.jpg)
3 Minimize text input in the interface
Why?
User has difficulty entering text so text is entered incorrectly or mistakes are made.
![Page 58: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/58.jpg)
3
FuncHonal DisabiliHes Context
User with motor disability (for
example, parHal paralysis, hand
tremor, lack of sensiHvity,
coordinaHon) has difficulty entering
informaHon.
Who does it helps?
![Page 59: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/59.jpg)
3
SituaHonal Disability Context
• Device has small keypad
which has limited
funcHonality
• The context of mobile could
be unpredictable
Who does it helps?
![Page 60: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/60.jpg)
• Avoid free text entry where possible.
3
• Provide pre-‐selected default values where possible.
• Specify a default text entry mode, language and/or input format, if the device is known to support it.
• Provide alternaHve means to enter text if possible
• Use keyboard shortcuts if supported by the device and browser
How do we achieve that?
![Page 61: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/61.jpg)
4 Use SemanHc Markup
Why?
If the page markup is invalid this will result in unpredictable and possibly incomplete presentaHon of the content.
![Page 62: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/62.jpg)
4
FuncHonal DisabiliHes Context: AssisHve technology or browser cannot handle invalid markup. Easier for disabled users using screen readers to understand the purpose of elements and quickly jump between different types of elements.
Who does it helps?
![Page 63: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/63.jpg)
4
SituaHonal Disability Context: Some older mobile browsers do not display content with invalid markup.
Who does it helps?
![Page 64: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/64.jpg)
EXAMPLE
HTML
4 How do we achieve that?
<form acHon="hop://example.com/donut" method="post"> <p> <input type="checkbox" name="flavor" id="choc" value="chocolate" /> <label for="choc">Chocolate</label><br/> <input type="checkbox" name="flavor" id="cream" value="cream"/> <label for="cream">Cream Filled</label><br/> <input type="checkbox" name="flavor" id="honey" value="honey"/> <label for="honey">Honey Glazed</label><br/> <input type="submit" value="Purchase Donuts"/> </p> </form>
![Page 65: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/65.jpg)
EXAMPLE android.view.accessibility.AccessibilityNodeProvider
4 ANDROID
This semanHc structure allows accessibility services to present a more useful interacHon model for users who are visually impaired.
How do we achieve that?
![Page 66: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/66.jpg)
5 Have a concise page content and page size
Why? User only sees small areas at a Hme, is unable to relate
different areas of a page, and so becomes
disoriented or has to scroll excessively.
![Page 67: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/67.jpg)
5
FuncHonal DisabiliHes Context User with restricted field of vision or using screen magnifier gets only small part of page or image at a Hme.
Who does it helps?
![Page 68: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/68.jpg)
SituaHonal Disability Context Mobile device has small screen, so not all inform can be displayed
5 Who does it helps?
![Page 69: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/69.jpg)
How do we achieve that? 5
• Clear and concise language, as mobile users are looking for a quick access to informaHon.
• Limit scrolling to one axis throughout the app (verHcal or horizontal axis) a
• Avoid image larger than the screen size
• Divide pages into usable but limited size porHons.
• PosiHon important things higher up and less important things lower down in scrolling views
• Create large clickable areas
![Page 70: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/70.jpg)
Do not insert funcHons that can only be managed via gestures. Always add a buoon/link 6
Why?
• Most gestures are not intuiHve
• Not recognized by many users
![Page 71: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/71.jpg)
FuncHonal DisabiliHes Context
• Blind users cannot use gestures at all
• Users with temporary disability cannot use gestures
• Gestures are guess work for most users
Who does it helps?
6
![Page 72: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/72.jpg)
SituaHonal DisabiliHes Context Gestures cannot be used in most of the outdoor or indoor context
Who does it helps?
6
![Page 73: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/73.jpg)
How do we achieve that? 6
• Use gestures which can be used even with buoon or link
• Don’t rely completely on gestures for the interacHon, have alternate interacHve mechanisms
![Page 74: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/74.jpg)
Ensure that it is possible to zoom the interface 7
Why?
Due to small screen, readability goes for a toss
![Page 75: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/75.jpg)
7 Who does it helps?
Zooming helps users who cannot read or see Hny leoers or have sight
disability
![Page 76: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/76.jpg)
HTML
7 How do we achieve that?
<meta name="viewport" value="iniHal-‐scale=1.0, minimum-‐scale=1.0, maximum-‐scale=2.0">
![Page 77: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/77.jpg)
CONCLUSION
![Page 78: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/78.jpg)
Mobile is for every . Think about it in your next applicaHon!
![Page 79: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/79.jpg)
Guidelines related to mobile accessibility
Web Content Accessibility Guidelines (WCAG) Mobile Web Best PracHces (MWBP) RelaHonship between WCAG and MWBP Widget Accessibility Guidelines Widget Usability Best PracHces Mobile Website Guidelines (University of AusHn)
![Page 80: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/80.jpg)
Device specific mobile accessibility guidelines
Android Designing for Accessibility Android Accessibility Blackberry Best PracHce Designing Accessible ApplicaHons iOS: Accessibility Programming Guide Nokia/Symbian: User Experience checklist for Touch and Keypad (PDFs)
![Page 81: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/81.jpg)
![Page 82: Mobile accessibility challenges and best practices v2](https://reader031.fdocuments.net/reader031/viewer/2022020116/558ead2d1a28ab88708b46d9/html5/thumbnails/82.jpg)
Shyamala Prayaga @pshyama