Here are the key guidelines for perceivable content:1. Provide text alternatives for non-text content like images2. Provide captions and audio descriptions for videos 3. Design pages that can be customized by users, for example with simpler layoutsThe goal is to make all content accessible to people with disabilities affecting vision, hearing, mobility, cognition, language, learning, etc. Things like images, videos, complex layouts can create barriers
Similaire à Here are the key guidelines for perceivable content:1. Provide text alternatives for non-text content like images2. Provide captions and audio descriptions for videos 3. Design pages that can be customized by users, for example with simpler layoutsThe goal is to make all content accessible to people with disabilities affecting vision, hearing, mobility, cognition, language, learning, etc. Things like images, videos, complex layouts can create barriers
JavaScript for ASP.NET programmers (webcast) uploadRuss Fustino
Similaire à Here are the key guidelines for perceivable content:1. Provide text alternatives for non-text content like images2. Provide captions and audio descriptions for videos 3. Design pages that can be customized by users, for example with simpler layoutsThe goal is to make all content accessible to people with disabilities affecting vision, hearing, mobility, cognition, language, learning, etc. Things like images, videos, complex layouts can create barriers (20)
Here are the key guidelines for perceivable content:1. Provide text alternatives for non-text content like images2. Provide captions and audio descriptions for videos 3. Design pages that can be customized by users, for example with simpler layoutsThe goal is to make all content accessible to people with disabilities affecting vision, hearing, mobility, cognition, language, learning, etc. Things like images, videos, complex layouts can create barriers
1. W3C - Intro and beyond
אייל סלע
מנהל פרויקטים, איגוד האינטרנט
הישראלי ומשרד ה- W3Cהישראלי
www.w3c.org.il 1
4. 1. About W3C
2. Standards (and drafts…)
– EmotionML
– HTML 5
– Semantic web
– WCAG 2.0
– Mobile Web Best Practices 1.0
– Some more
3. + תמונה כוללתWhat Can You Do?
www.w3c.org.il 4
5. W3C
ארגון בינלאומי •
כ-053 ארגונים •
פורום ניטראלי ליצירת תקני רשת באינטרנט. •
משימה: •
להוביל את הרשת למיצוי הפוטנציאל על ידי פיתוח
פרוטוקולים וקווים מנחים שיאפשרו את צמיחתה
לטווח ארוך.
www.w3c.org.il 5
6. CSS HTML XML
XSLT OWL RDF
DOM PNG
SVG WCAG
www.w3c.org.il 6
9. המשרד הישראלי
• הוקם ב-9991
• משנת 8002 -איגוד האינטרנט הישראלי
• מטרות :
1. להביא ליישום המלצות
2. ערוץ קשר
3. לוקליזציה ותקני עברית
www.w3c.org.il 9
11. 1.Interest
– (Member Submissions , Team monitors , Workshops)
– (proposal, inside consensus)
2.new Activity / Group
- (working/ interest/ coordination/incubator)
- Charter
- Members, Invited Experts, and Team.
3. Recommendation track
j.mp/w3cdoc
www.w3c.org.il 11
12. Recommendation track
appropriate for widespread
deployment and promote
•Review -sufficient implementation
experience
•implementation -sent to the Advisory
Committee for review
•interoperability.
-feedback
- first
implementation
-Fulfill all requirements
-seeks technical review
bit.ly/w3cpro
www.w3c.org.il 12
21. HTML 4 = static pages
HTML 5 = Runtime environments
- (like Flash, Java J2ME/MIDP, Silverlight).
- No downloads, in the browser.
www.w3c.org.il 21
22. Design Principles
1. Support existing content
2. Ensure interoperability
Web, Mobile, Many browsers.
3. Precisely define browser behavior
Example: how “table” or “form” should act.
4. Handle errors
Today 90% of the web is not “correct”
5. Evolution not revolution
Keep the past.
Enable the future.
j.mp/w3cml5
www.w3c.org.il 22
23. תגיות עם משמעות סמנטית
• נגיש
• סמנטי
j.mp/w3cmnt
www.w3c.org.il 32
24. Absent Elements
• basefont
• big “their effect is purely
• center presentational and their
• font function is better
• s handled by CSS"
• strike
• tt
• u
www.w3c.org.il 24
32. Is about…
machine interpretability of Web
content.
applications will
process the content of information
instead of just
presenting it to humans.
j.mp/w3cowl
32 www.w3c.org.il
36. The element of the Semantic Web
Resource Description Framework (RDF)
<http://www.productivewise.com/> <http://creativecommons.org/ns#attributionName> "Eyal Sela" .
36 www.w3c.org.il
57. POWDER
Protocol for Web Description Resources —mechanism to describe and
discover Web resources and helps the users to make a decision whether a given
resource is of interest.
Profile matching
Grouping
Data retrieval efficiency
Semantic Annotation
www.w3c.org.il 57
60. skos
Many knowledge organization systems share a similar structure, and are used in
similar applications. SKOS captures much of this similarity and makes it explicit, to
enable data and technology sharing across diverse applications.
classification
Taxonomies
Thesauri
60 www.w3c.org.il
62. OWL use?
Now:
have complex data + willing to
learn
Future (years):
all organizations and professionals
who produce/consume data
j.mp/w3cowld
62 www.w3c.org.il
63. Web 2.0 web 3.0
you (will) have a
personal Website, with
your photos, your family
tree, your business
details, and aggregators
then (will) turn this into
added value by finding
the links across the
whole web.
]Economist 2008[ )illustration by David Simonds(
j.mp/w3cweb
63 www.w3c.org.il
68. 1 Perceivable
1.1 Provide text alternatives for any non-text
content so that it can be changed into other forms
people need, such as large print, braille, speech,
symbols or simpler language.
1.2 Provide alternatives for time-based media.
1.3 Create content that can be presented in
different ways (for example simpler layout)
without losing information or structure.
1.4 Make it easier for users to see and hear content
including separating foreground from background.
www.w3c.org.il 68
69. 2 Operable
2.1 Make all functionality available from a keyboard.
2.2 Provide users enough time to read and use
content.
2.3 Do not design content in a way that is known to
cause seizures.
2.4 Provide ways to help users navigate, find content,
and determine where they are.
www.w3c.org.il 69
70. 3 Understandable
3.1 Make text content readable and
understandable.
3.2 Make Web pages appear and operate in
predictable ways.
3.3 Help users avoid and correct mistakes.
www.w3c.org.il 70
71. 4 Robust
4.1 Maximize compatibility with current and future
user agents, including assistive technologies.
www.w3c.org.il 71
78. Some practices…
• [CAPABILITIES] Exploit device capabilities to
provide an enhanced user experience.
• [TESTING] Carry out testing on actual
devices as well as emulators.
• [URIS] Keep the URIs of site entry points
short.
www.w3c.org.il 78
79. Some practices…
• [NAVBAR] Provide only minimal navigation
at the top of the page.
• [BALANCE] Take into account the trade-off
between having too many links on a page
and asking the user to follow too many links
to reach what they are looking for.
• [NAVIGATION] Provide consistent navigation
mechanisms.
www.w3c.org.il 79
80. Some practices…
• [[ACCESS_KEYS] Assign access keys to links
in navigational menus and frequently
accessed functionality.
• [LINK_TARGET_FORMAT] Note the target
file's format unless you know the device
supports it.
• [POP_UPS] Do not cause pop-ups or other
windows to appear and do not change the
current window without informing the user.
www.w3c.org.il 80
81. Some practices…
• [AUTO_REFRESH] Do not create periodically
auto-refreshing pages, unless you have
informed the user and provided a means of
stopping it.
• [SUITABLE] Ensure that content is suitable
for use in a mobile context.
• [CLARITY] Use clear and simple language.
www.w3c.org.il 81
88. Authoring Tool Accessibility
Guidelines (ATAG) 2.0
• Ensure that automatically generated content is
accessible.
• Guide authors to create accessible content.
• Assist authors in checking for accessibility problems.
• Assist authors with managing alternative
content for non-text content.
www.w3c.org.il 88
89. Further into the future
not intended for implementation yet
Geolocation API Specification define a secure and
privacy-sensitive interface for using client-side
location information in location-aware Web applications
Voice Extensible Markup Language (VoiceXML) 3.0 interactive media dialogs that
feature synthesized speech, recognition of spoken and DTMF key input, telephony, mixed
initiative conversations, and recording and presentation of a variety of media formats
including digitized audio, and digitized video.
User Agent Accessibility Guidelines (UAAG) 2.0
XML Signature Best Practices best practices for implementers and users of the XML
Signature specification
www.w3c.org.il 89
90. Interesting Interest group (13)
you can participate
• Internationalization
• Mobile Web For Social Development (MW4D)
• Semantic Web
• Semantic Web Health Care and Life Sciences
• Web Accessibility Initiative
• Research and Development
• eGovernment Interest Group
• ...
j.mp/w3cac
www.w3c.org.il 90
91. Incubator groups
• Social Web
• Rich Web Application Backplane
( a set of common building blocks for web applications.)
• Open Web Education Alliance
• Semantic Sensor Network
j.mp/w3cin
www.w3c.org.il 91
95. What Can You Do?
– Public review (drafts, last calls…)
– Mailing lists & newsletter
– Implementations
– Interest &incubator groups
– Through us
– Join as a member
:בארץ
• תרגם
• הרצאות
• שת"פ איתנו
www.w3c.org.il 95