2. Prologue
Most portal interfaces are still based on
HTML or poor XHTML vs. well-formed XHTML
Strict.
Lots of table-based layout vs. CSS-based
positioning for column and portlet layout.
I call this: “jumping almost ten years
back in the past”.
past”
Accessib... what?
2
3. 1. Guess who... applies MVC
Actor 1A: famous “enterprise portal solution
that is used in more than 100,000
deployments worldwide”
Evidence 1A: a JSP file from the backoffice.
<c:if test="<%= !themeDisplay.isStateExclusive() && !
themeDisplay.isStatePopUp() %>"> [...]
<table class="lfrctrlpanel <%= panelCategory %>"> [...]
private static boolean _hasPortlet(String portletId, String
category, ThemeDisplay themeDisplay) throws Exception {
List<Portlet> portlets =
PortalUtil.getControlPanelPortlets(category, themeDisplay);
[...]
return false;
}
[ad libitum...]
3
5. 1. Guess who... applies MVC
Try and tell: who does apply the MVC pattern
even inside the presentation layer ?
Right! jAPS 2.0 does.
You won't find a single bit of Java code in a
JSP. A presentation layer specialist
doesn't have to go for energy drinks just to
understand what's the matter with a file from
a Web GUI.
Your own Accessibility and Usability Guru
must focus on Accessibility and Usability,
rather than on Java-code-in-a-JSP decrypting
tecniques.
5
6. 2. Guess who... lives in the past
Actor 2A: famous “enterprise portal solution
that is used…”
Evidence 2A: markup from the frontend.
<!DOCTYPE html PUBLIC "//W3C//DTD XHTML 1.0 Transitional//EN" "
http://www.w3.org/TR/xhtml1/DTD/xhtml1transitional.dtd">
[...] <body class="blue controlsvisible guestcommunity public
page">
<p class="welcomeintro">CENSORED is a complete allinone open
source enterprise portal solution that is used in more than
100,000 deployments worldwide. [...] to create webbased solutions
for enterprise needs, including:</p>
<table class="welcomegrid">
<tbody>
<tr class="header">
<td width="50%">INSTANT WEBSITES</td><td
width="50%">SOCIAL NETWORKS</td></tr><tr><td class="web
publishing" valign="top"> [ad libitum...]
6
7. 2. Guess who... lives in the past
Actor 2B: jAPS 2.0
Evidence 2B: markup from the frontend.
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE html PUBLIC "//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
[...] <body>
[...] <div id="header">
<h1>Comune di Villamarina</h1>
<p>Official Site</p>
<div class="noscreen">
<p>[ <a href="#a4" id="a0">Go to Contents</a> ]</p>
[ad libitum...]
7
8. 2. Guess who... lives in the past
Try and tell: who does live almost ten years
in the past as defined in the Prologue?
Right! The famous “enterprise portal solution
that is used… whatever” does.
XHTML elements do have meanings. That is,
meanings
a table is meant to be a table. Not a
table
division in the page layout. That's the div
div
element.
Users with disabilities - like your stereotypical
blind friend and your not-so-stereotypical and
very tired, sleepy top manager at 3.00 AM -
will thank you for an accessible platform.
8
9. Epilogue
Most portal interfaces are still based on
HTML or poor XHTML vs. well-formed XHTML
Strict. Not jAPS 2.0.
Lots of table-based layout vs. CSS-based
positioning for column and portlet layout. Not
in jAPS 2.0.
I call this: “Sailing towards the future”.
future”
I call this the Web, made Accessible.
Accessible
9
10. Thank You!
Image URL: http://www.yumaaz.gov/Images/General/ss-1003945-futureSign.jpg
www.japsportal .org
< Do It The jAPS Way />
10