298:
557:
432:
379:
30:
284:"Web accessibility means that people with disabilities can use the Web. More specifically, Web accessibility means that people with disabilities can perceive, understand, navigate, and interact with the Web, and that they can contribute to the Web. Web accessibility also benefits others, including older people with changing abilities due to aging."
444:
293:
First of all, it must be clear that many people can be led to read or edit
Knowledge (XXG) with very different means from the average Web user as they are usually seen. They can be blind, visually impaired, deaf, or physically disabled. To make the most of the Web's resources, specifically here to
422:
Overall, the most recent studies estimate that no more than 3% of websites that can be considered as sufficiently accessible (A accessibility level). Knowledge (XXG) does not yet present in this category, although its potential accessibility is important.
150:
494:
Structuring data tables in a semantic way – or instead making it clear that a table is used for layout only – will make the content understandable by everyone. This is especially true for screen reader users. It also improves reuse of the
524:
Accessibility is only partially automatable and relies on everyday changes. While accessibility should not be a burden for editors, it can be encouraged through best practices. Those best practices slowly becomes common practice.
140:
127:
459:) which has both strengths and shortcomings in matters of accessibility. But its improvement does not rely solely on software developers. Each Knowledge (XXG) user (at all levels) can contribute to its improvement.
487:
Providing explicit legends for images allows all users who do not have access to these images to get the most important informations. It's particularly important for images containing a lot of informations such as
259:
564:
Accessibility promotes appropriate use of different technologies (HTML, CSS, Javascript, images, audio, video) that facilitates the reuse of the content itself, when it comes to distribute through other media.
133:
188:
109:
74:
178:
396:
Content (like text, tables, links, graphics) perfectly understandable when displayed in a graphical browser can completely lose its meaning when rendered by another type of browser, or read by
503:
bear similar responsibility. However, the impact of widely used templates is detrimental. Thus, improving – and monitoring changes made to – the most widely used templates is a top priority.
252:
510:
writers too, since a script generating active components of the interface (such as links, buttons and such) needs to be usable regardless of input device (keyboard or mouse, etc.).
245:
193:
368:
For the technical aids to be able to play their role, the content of Web pages must follow various technical requirements. These have been developed as an international standard (
226:
198:
145:
183:
160:
518:
390:
Some links may not be used without a mouse or an equivalent pointing device. Customers using an input device like a keyboard won't be able to follow them.
69:
95:
90:
348:
In fact, there are many different navigation help tools for the Web, corresponding to many different disabilities. Thus, accessibility does not means
104:
333:
Most Web browsers also offer the possibility to adapt the consultation of a website, to a certain degree: with or without images, with or without
55:
45:
17:
491:
Writing explicit links titles makes the navigation understandable to users who access them directly out of context (users of screen readers).
537:
Accessible use of color improves readability for all users with a screen with poor contrast. The colors will also print nicely in grayscale.
393:
Forms can be very difficult to understand, or even unusable, without the informations contained in its graphics and visual presentation.
598:
466:
daily play a central role. Several accessibility guidelines can only be applied on a per-case basis by the editors. For example:
360:
be perceived, understood and usable with all tools, so that no user is penalized as long as he uses a tool that fits his needs.
221:
375:
When these rules are not respected, disabled contributors and readers of the encyclopedia encounter difficulties including:
372:), in order to be compatible with other requirements of a website's quality (content, usability, security, design, etc.).
369:
277:
568:
In conclusion, improving accessibility is an occasion to improve the quality of
Knowledge (XXG) on a broader meaning.
316:
35:
313:, which use speech synthesis to reproduce Web pages and make them interactive (following links, using forms, etc.).
452:
480:. It enables a speech synthesis to pronounce the words correctly (and have several other uses such as improving
443:
40:
216:
436:
387:
Images may not be "read" by using technologies like a screen reader. Substantial information may be lost.
297:
546:
Text alternatives and legends for images are useful to low bandwidth users who can't download images.
231:
329:
equipment or software to magnify the pages visited, or simply the zoom function of their browser.
403:
A text whose font size was determined inappropriately (with pixels instead of relative size or
481:
397:
302:
407:) will not be readable by users with low vision who needs to zoom into or magnify the page.
556:
378:
276:" has different meanings. Throughout this project, we stick to the definition of W3C's
592:
474:
447:
Example of color usage and CSS styles (top) not accessible (down, result without CSS)
310:
273:
540:
431:
294:
read articles or use the edit functions, they use equipment and software such as:
583:
517:
developers (hired and volunteers) also play an crucial role that is detailed in
533:
Benefits induced from these improvements far exceeds users with disabilities:
415:
411:
338:
323:
456:
342:
29:
352:
a website for one disability or another. In a certain way, it rather means
470:
Mention that a quotation is not in
English and indicate its language with
282:
555:
442:
430:
377:
296:
322:
special input devices instead of a keyboard and/or a mouse (see
356:: the website is designed in such a way that his contents can
334:
382:
Sample picture (data chart) conveying important informations.
577:
549:
Making correct layout tables benefits to all mobile users.
25:
560:
Keyboard with widened keys for partially sighted users.
414:
of text or images may not be correctly perceived by a
289:
How can people with disabilities use
Knowledge (XXG)?
253:
8:
543:independence benefits to all keyboard users.
324:Motor Disabilities, Assistive Technologies
260:
246:
51:
529:Who will benefit from those improvements?
18:Knowledge (XXG):WikiProject Accessibility
364:What kind of problems do they encounter?
54:
462:Contributors who write or modify the
7:
24:
578:Introduction to Web Accessibility
427:How can we improve accessibility?
301:Login to Knowledge (XXG) using a
435:Knowledge (XXG) accessed with a
410:Information conveyed by certain
28:
1:
584:Wikimedia Foundation Mission
451:Knowledge (XXG) relies on a
370:Web Accessibility Initiative
317:Refreshable Braille displays
278:Web Accessibility Initiative
519:introduction for developers
105:Alternative text for images
615:
134:Most widely used templates
599:WikiProject Accessibility
453:content management system
56:WikiProject Accessibility
319:, with the same purpose;
189:Resources and references
484:'s language detection).
75:FAQ and common pitfalls
561:
448:
440:
437:text-based web browser
412:combinations of colors
383:
306:
286:
65:What is accessibility?
559:
446:
434:
381:
300:
179:Manual of Style draft
161:Infobox accessibility
110:Data tables tutorial
70:Main discussion page
341:, with an enlarged
128:Template priorities
122:Template guidelines
562:
516:
509:
502:
465:
449:
441:
398:speech synthesizer
384:
337:, with or without
307:
272:The general term "
222:Keyboard shortcuts
211:For impaired users
85:Article guidelines
514:
507:
500:
463:
270:
269:
606:
482:Google Translate
479:
473:
406:
303:screen magnifier
262:
255:
248:
99:
52:
32:
614:
613:
609:
608:
607:
605:
604:
603:
589:
588:
574:
531:
477:
471:
429:
404:
366:
291:
266:
237:
236:
212:
204:
203:
194:Policy proposal
174:
166:
165:
157:
156:
123:
115:
114:
97:
96:Manual of Style
86:
50:
22:
21:
20:
12:
11:
5:
612:
610:
602:
601:
591:
590:
587:
586:
581:
573:
570:
554:
553:
552:And much more.
550:
547:
544:
538:
530:
527:
497:
496:
492:
489:
485:
428:
425:
420:
419:
408:
401:
394:
391:
388:
365:
362:
355:
351:
331:
330:
327:
320:
314:
311:screen readers
290:
287:
268:
267:
265:
264:
257:
250:
242:
239:
238:
235:
234:
229:
224:
219:
213:
210:
209:
206:
205:
202:
201:
196:
191:
186:
181:
175:
172:
171:
168:
167:
164:
163:
158:
155:
154:
148:
143:
136:
132:
130:
124:
121:
120:
117:
116:
113:
112:
107:
102:
93:
91:Dos and don'ts
87:
84:
83:
80:
79:
78:
77:
72:
67:
59:
58:
49:
48:
43:
38:
36:Collaborations
33:
23:
15:
14:
13:
10:
9:
6:
4:
3:
2:
611:
600:
597:
596:
594:
585:
582:
579:
576:
575:
571:
569:
566:
558:
551:
548:
545:
542:
539:
536:
535:
534:
528:
526:
522:
520:
511:
504:
493:
490:
486:
483:
476:
469:
468:
467:
460:
458:
454:
445:
438:
433:
426:
424:
417:
413:
409:
402:
399:
395:
392:
389:
386:
385:
380:
376:
373:
371:
363:
361:
359:
353:
349:
346:
345:, and so on.
344:
340:
336:
328:
325:
321:
318:
315:
312:
309:
308:
304:
299:
295:
288:
285:
281:
279:
275:
274:accessibility
263:
258:
256:
251:
249:
244:
243:
241:
240:
233:
230:
228:
225:
223:
220:
218:
215:
214:
208:
207:
200:
199:Popular pages
197:
195:
192:
190:
187:
185:
182:
180:
177:
176:
170:
169:
162:
159:
152:
149:
147:
144:
142:
138:
137:
135:
131:
129:
126:
125:
119:
118:
111:
108:
106:
103:
101:
100:Accessibility
94:
92:
89:
88:
82:
81:
76:
73:
71:
68:
66:
63:
62:
61:
60:
57:
53:
47:
46:Accessibility
44:
42:
39:
37:
34:
31:
27:
26:
19:
567:
563:
541:Input device
532:
523:
512:
505:
498:
461:
450:
421:
374:
367:
357:
347:
332:
292:
283:
271:
227:Style sheets
173:Coordination
64:
41:WikiProjects
499:Authors of
184:Methodology
488:timelines.
416:colorblind
354:neutrality
350:optimising
339:Javascript
217:Using JAWS
580:, WebAIM.
515:MediaWiki
501:templates
457:MediaWiki
343:font size
326:, WebAIM)
232:Toggle VF
151:Watchlist
593:Category
572:See also
495:content.
464:contents
358:a priori
146:200–1000
280:(WAI):
141:Top 200
508:script
418:user.
16:<
513:The
506:The
475:lang
335:CSS
595::
521:.
478:}}
472:{{
405:em
98:/
455:(
439:.
400:.
305:.
261:e
254:t
247:v
153:)
139:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
