[prev in list] [next in list] [prev in thread] [next in thread]
List: sonar-scm
Subject: [sonar-scm] [jira] (SONAR-6066) Usability and accessibility issues
From: "Oliver Brandt (JIRA)" <jira () codehaus ! org>
Date: 2015-01-30 20:30:18
Message-ID: JIRA.159179.1421788243275.10236.1422649818743 () codehaus01 ! managed ! contegix ! com
[Download RAW message or body]
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" \
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html \
xmlns="http://www.w3.org/1999/xhtml"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, \
maximum-scale=1.0" /> <base href="https://jira.codehaus.org" /> <title>Message \
Title</title> </head>
<body class="jira" style="color: #333; font-family: Arial, sans-serif; font-size: \
14px; line-height: 1.429"> <table id="background-table" cellpadding="0" \
cellspacing="0" width="100%" style="border-collapse: collapse; mso-table-lspace: 0pt; \
mso-table-rspace: 0pt; background-color: #f5f5f5; border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt"> <!-- header here -->
<tr>
<td id="header-pattern-container" style="padding: 0px; \
border-collapse: collapse; padding: 10px 20px"> <table id="header-pattern" \
cellspacing="0" cellpadding="0" border="0" style="border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt"> <tr>
<td id="header-avatar-image-container" valign="top" \
style="padding: 0px; border-collapse: collapse; vertical-align: top; width: 32px; \
padding-right: 8px"> <img id="header-avatar-image" class="image_fix" \
src="https://jira.codehaus.org/secure/useravatar?avatarId=10232" height="32" \
width="32" border="0" style="border-radius: 3px; vertical-align: top" /> </td>
<td id="header-text-container" valign="middle" \
style="padding: 0px; border-collapse: collapse; vertical-align: middle; font-family: \
Arial, sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; \
mso-text-raise: 1px"> <a class="user-hover" rel="brevilo" id="email_brevilo" \
href="https://jira.codehaus.org/secure/ViewProfile.jspa?name=brevilo" \
style="color:#005500;; color: #3b73af; text-decoration: none">Oliver Brandt</a> \
<strong>commented</strong> on an issue </td>
</tr>
</table>
</td>
</tr>
<tr>
<td id="email-content-container" style="padding: 0px; \
border-collapse: collapse; padding: 0 20px"> <table id="email-content-table" \
cellspacing="0" cellpadding="0" border="0" width="100%" style="border-collapse: \
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; border-spacing: 0; \
border-collapse: separate"> <tr>
<!-- there needs to be content in the cell for it to \
render in some clients --> <td class="email-content-rounded-top mobile-expand" \
style="padding: 0px; border-collapse: collapse; color: #fff; padding: 0 15px 0 16px; \
height: 15px; background-color: #fff; border-left: 1px solid #ccc; border-top: 1px \
solid #ccc; border-right: 1px solid #ccc; border-bottom: 0; border-top-right-radius: \
5px; border-top-left-radius: 5px; height: 10px; line-height: 10px; padding: 0 15px 0 \
16px; mso-line-height-rule: exactly">
</td>
</tr>
<tr>
<td class="email-content-main mobile-expand " \
style="padding: 0px; border-collapse: collapse; border-left: 1px solid #ccc; \
border-right: 1px solid #ccc; border-top: 0; border-bottom: 0; padding: 0 15px 0 \
16px; background-color: #fff"> <table class="page-title-pattern" cellspacing="0" \
cellpadding="0" border="0" width="100%" style="border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt"> <tr>
<td style="vertical-align: top;; padding: \
0px; border-collapse: collapse; padding-right: 5px; font-size: 20px; line-height: \
30px; mso-line-height-rule: exactly" class="page-title-pattern-header-container"> \
<span class="page-title-pattern-header" style="font-family: Arial, sans-serif; \
padding: 0; font-size: 20px; line-height: 30px; mso-text-raise: 2px; \
mso-line-height-rule: exactly; vertical-align: middle"> <a \
href="https://jira.codehaus.org/browse/SONAR-6066" style="color: #3b73af; \
text-decoration: none">Re: Usability and accessibility issues</a> </span> </td>
</tr>
</table>
</td>
</tr>
<tr>
<td id="text-paragraph-pattern-top" \
class="email-content-main mobile-expand comment-top-pattern" style="padding: 0px; \
border-collapse: collapse; border-left: 1px solid #ccc; border-right: 1px solid #ccc; \
border-top: 0; border-bottom: 0; padding: 0 15px 0 16px; background-color: #fff; \
border-bottom: none; padding-bottom: 0"> <table class="text-paragraph-pattern" \
cellspacing="0" cellpadding="0" border="0" width="100%" style="border-collapse: \
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; font-family: Arial, \
sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; \
mso-text-raise: 2px"> <tr>
<td class="text-paragraph-pattern-container \
mobile-resize-text " style="padding: 0px; border-collapse: collapse; padding: 0 0 \
10px 0"> <p style="margin: 10px 0 0 0">I'll pick up from Michael by listing the most \
severe findings from the \
"Prüfbericht_Barrierefreiheit_SonarQube_4.5.pdf"</p>
<p style="margin: 10px 0 0 0"><b>Severity \
(p 8, Tabelle 2-1):</b></p> <ul>
<li>
*- - - *: An accessibility block \
leads to a relevant function not being usable or a relevant information being \
imperceptible. Such a problem should definitely be fixed to enable the affected users \
to use the application. </li>
<li>
<b>- -</b>: An accessibility \
obstacle leads to a relevant information being hardly understandable or hardly \
perceptible or a relevant function or information can only be used by a workaround. \
Such a problem souhld be fixed to enable the affected users to use the application \
more efficiently. </li>
<li>
<b>-</b>: A small accessibility \
restriction leads to information or functions becoming accessible by certain user \
actions (e.g. changeing browser settings, changing settings of assistive technologies \
or training) or leads to the user being disturbed or distracted. Such a problem \
should be fixed with low priority. </li>
</ul>
<p style="margin: 10px 0 0 0"><b>3 Test \
Results</b></p> <p style="margin: 10px 0 0 0">The test results contain individual \
severities for differently affected users: visually impaired useres (<b>S</b>), blind \
users (<b>B</b>), users with movement disorders (<b>M</b>) and deaf users \
(<b>G</b>).</p>
<p style="margin: 10px 0 0 0"><b>3.1 \
Problems</b></p> <p style="margin: 10px 0 0 0"><b>[1] A lof of interaktive elements \
cannot be operated via keyboard.</b><br /> A lot of interactive elements do not use \
the HTML standard elements for links, buttons and form field. Therefore they cannot \
be activated via keyboard. A lot of interactive elements use <span> or \
<div> elements coupled with event handlers only activatable by using the mouse. \
Another reason is the use of <a> elements without href-attribute which are also \
not reachable by keyboard. <br /> Examples:</p> <ul>
<li>
p 11, Abblidung 3-1: In the \
source code area most of the intractive elements are not reachable by keyboard, so \
most of the functionality is not usable when using a keyboard only. </li>
<li>
p 12, Abblidung 3-2 on the top: \
On some pages the buttons used for filtering the search results are not reachable by \
keyboard. </li>
<li>
Abblidung 3-2 lower left: The \
search results do not get the focus and are not reachable by keyboard, so the details \
cannot be accessed by keyboard users. They also cannot scroll the result list. As \
scrolling the list fetches more results, keyboard users are not able to see all \
results. </li>
<li>
Abbildung 3-1 top left: The \
options to sort the results are not reachable by keyboard. </li>
<li>
p 13, Abbildung 3-3: Blind users \
are not able to operate the combined input fields due to the following reasons (just \
the most impotant reasons listed): <ul>
<li>
The form fields are not \
linked with their descriptions, so blind users are not able to discern the meaning of \
a certain field. </li>
<li>
If text is entered into a \
form field, the autocompletion kicks in and updates the list. This update is not \
discernible with a screen reader. Furthermore, the elements are not reachable by \
keyboard. </li>
<li>
If the field is left, the \
first matching element from the list is used as field value. Blind users cannot \
discern that changed from the input value. </li>
<li>
After inputting a value, \
the fields are no longer reachable by keyboard. </li>
</ul>
</li>
<li>
p 13, Abblidung 3-4: All links \
regarding filter options reachable by keyboard cannot be operated by blind users as \
the screen reader does not output anything for these elements. After activating a \
link by keyboard while using a screen reader, the focus is not set to the first item \
in the recently openend sub-menu. Blind users are not able to reach these elements \
with the cursor or tab keys. </li>
<li>
p 14, Abbildung 3-5: Blind users \
are not able to discern menu items opening a new page from items opening a sub-menu, \
because the are not able to perceive the arrow icon. </li>
<li>
p 14, Abbildung 3-6: The \
"Dependency Structure Matrix" elements ar not reachable by keyboard. </li>
<li>
p 14, Abbildung 3-7: The coloured \
"Treemap" blocks are not navigable by keyboard. </li>
<li>
p 15, Abbildung 3-8: The links \
for opening and closing of subordinate elements are not reachable by keyboard on some \
pages. </li>
<li>
p 15, Abbildung 3-9: Some \
interactive elements are shown only when the mouse is hovering over otherwise empty \
parts. Therefore these elements are not discernable and usable by keyboard. </li>
<li>
p 15, Abbildung 3-10: Some \
elements are not reachable by keyboard even when standard elements for links, form \
elements and buttons are used. The reason for this is the attribute tabindex=-1. \
</li> <li>
p 16, Abbildung 3-11, top right: \
Links without href attribute are not reachable by keyboard.<br /> Abblidung 3-11, top \
left: Drag & Drop cannot be used via keyboard. Therefore the ordering of the \
dashboard widgets cannot be changed by keyboard. </li>
<li>
Abblidung 3-1, middle: Some \
drop-down-lists and combined input fields cannot be reached by keyboard after \
selecting an item. The same holds true for the deletion icon ("x"). The \
reason for this is the attribute tabindex=-1. </li>
</ul>
<p style="margin: 10px 0 0 0">These \
findings are seen as an accessibility block, since blind users or users with a \
movement disorder using only a keyboard are not able to use the aplication to its \
full extent.</p>
<p style="margin: 10px 0 0 \
0">Recommendations (only the most important ones):</p> <ul>
<li>
All interactive elements should \
be selectable by keyboard (tab key). </li>
<li>
All functions should be \
activatable by keyboard (space or enter key).<br /> Interactive elements shouls be \
implemented using the HTML elements <a>, <button> or <input> . \
</li> <li>
HTML elemnts should be used \
according to their purpose. E.g. a selection list should be implemented using \
<option> and <select> instead of as a link, button or input field. </li>
<li>
For some interactive elements \
like combined input fields with autocompletion, no corresponding HTML elements are \
available. These elements should be labeled according to ARIA. Furthermore, those \
elements should be able to be operated according to the usual conventions. Further \
infos: <a href="http://www.w3.org/TR/wai-aria/roles#combobox" class="external-link" \
rel="nofollow" style="color: #3b73af; text-decoration: \
none">http://www.w3.org/TR/wai-aria/roles#combobox</a>, <a \
href="http://www.w3.org/TR/wai-aria-practices/#combobox" class="external-link" \
rel="nofollow" style="color: #3b73af; text-decoration: \
none">http://www.w3.org/TR/wai-aria-practices/#combobox</a>. Examples can be found at \
<a href="http://oaa.accessibility.org/examples/role/77" class="external-link" \
rel="nofollow" style="color: #3b73af; text-decoration: \
none">http://oaa.accessibility.org/examples/role/77</a> and <a \
href="http://test.cita.illinois.edu/aria/combobox" class="external-link" \
rel="nofollow" style="color: #3b73af; text-decoration: \
none">http://test.cita.illinois.edu/aria/combobox</a> </li>
<li>
Each link should contain a href \
attribute in its <a> element. </li>
<li>
The attribute tabindex=-1 should \
be removed from all interactive elements. </li>
<li>
For all Drag&Drop \
functionalities an alternative method for keyborad users should be provided. </li>
<li>
Fetching additional data should \
be possible without the need for scrolling. </li>
<li>
Regarding sub-menus:
<ul>
<li>
When oprning a sub-menu \
the first item should be focussed. </li>
<li>
All items should be \
reachable by cursor or tab keys and be activatable by the enter or space key. </li>
<li>
A correct output by \
screen reader should be assured, e.g. for filtering options. </li>
<li>
A menu item having a \
sub-menu should be marked with the ARIA property aria-haspopup. </li>
</ul>
</li>
<li>
All interactive elements should \
be discernible at all times. </li>
</ul>
<p style="margin: 10px 0 0 0"><b>[2] Some \
pages contaion keyboard traps.</b><br /> After loading the pages "Rules", \
"Issues" and "Measures" the focus is set automaticallly on the \
search and filter area. Using a keyboard the navigation is only possible between the \
first and the last interactive element in this area. Any other element before or \
after that area is not reachable using only the keyboard.</p> <p style="margin: 10px \
0 0 0">Recommendation: Leaving the search and filter area should be possible by using \
the tab key.</p> <p style="margin: 10px 0 0 0"><b>[3] Some content is hardly \
discernible using a screen reader.</b><br /> Screen readers analyse the HTML code and \
processes it to be suitable for blind users. Since for some content no or not enough \
information is provided, the output is not always comprehensible.</p> <ul>
<li>
p 19, Abbildung 3-13: Most icons \
are not discernible to blind users as they are implemented using the CSS property \
:content which is not processed by the screen reader. A lot of these icons are used \
to activate certain functions of the application (Abblidung 3-13, on the right), \
rendering these functions unreachable for blind users. Are these icons used as part \
of a link, the function can beactivated, but its purpose is not discerniable. </li>
<li>
p 19, Abblidung 3-14: Blind users \
are not able to discern the content of filter options as these are not output by the \
screen reader while tabbing these elements. This stems from changing the standard \
function of the tab keyby Javascript to just highlight the elements visually without \
focussing them. This also hold true for sub-menus opened after activation a filter \
element. </li>
<li>
p 20, Abblidung 3-15: Blind users \
are not able to discern the summary on the dashboard, since it is not at the \
beginning of the page, the screen reader does not output the colouring and it does \
not have a heading. </li>
</ul>
<p style="margin: 10px 0 0 0">These \
findings are seen as an accessibility obstacle.</p>
<p style="margin: 10px 0 0 \
0">Recommendations:</p> <ul>
<li>
The icons should be included as \
graphics with a meaningful alternative text. </li>
<li>
Icons being used as part of a \
link should have an empty alt attribute. The purpose of the link should be describe \
in the title attribute of the <a> element. </li>
<li>
As an alternative meaningful \
textual decriptions should be used with icons which can be hidden from not blind \
users via CSS attributes. </li>
<li>
Another possibility would be the \
use of the ARIA property aria-label for icons <a \
href="http://www.w3.org.TR/wai-aria/states_and_properties/#aria_label" \
class="external-link" rel="nofollow" style="color: #3b73af; text-decoration: \
none">http://www.w3.org.TR/wai-aria/states_and_properties/#aria_label</a> </li>
<li>
The filter options should be \
implemented using the HTML elements <a> or <button>. </li>
<li>
The summary on the dashboard \
should be located in the HTML source right after the navigation menu and get a \
meaningful heading. </li>
</ul>
<p style="margin: 10px 0 0 0"><b>[4] \
Headings are not marked as such.</b><br /> The pages are structured visually by \
hadings and blocks. Blind users are not able to discern these visual hints and are \
using screen reader functionality to navigate quickly between headings. If there are \
no heading available in the HTML markup this functionality is not available resulting \
in inefficient navigation for blind users.</p> <ul>
<li>
p 21, Abblidung 3-16: Some pages \
do not have a heading at all. </li>
<li>
Some pages use heading markup for \
non-header elements. E.g. information ragrding the snapshot (p 21, Abbildung 3-17, \
top), drop down lists (Abbildung 3-17, right) or links in the source code view (p22, \
Abildung 3-18, bottom). </li>
<li>
On some pages the headings are \
not marked according to their hierarchy. E.g. the rules headings ind the source code \
view are marked as <h1> (p 22, Abbildung 3-18, top). </li>
</ul>
<p style="margin: 10px 0 0 0">These \
findings are seen as an accessibility obstacle.</p>
<p style="margin: 10px 0 0 \
0">Recommendations:</p> <ul>
<li>
The headings <h1> to \
<h4> should be used according to their hierarchy. </li>
<li>
Each page should have a \
<h1> heading acoording to its contents. </li>
<li>
Each block should have a separate \
heading in order for blind users being able to easily navigate to the desired block. \
These headings could eventually made invisible to other users via CSS. </li>
<li>
Each pop-up should get a \
<h2> heading in order for blind users to discern them more easily. </li>
<li>
Content apart from headings \
should not be marked as a heading. </li>
<li>
Headings should not contain any \
interactive element. </li>
</ul>
<p style="margin: 10px 0 0 0"><b>[5] Form \
fields are not linked with their labels.</b><br /> Blind users need a corresponding \
description for each form field. Screen readers are not able to output the labels due \
to the following reasons:</p> <ul>
<li>
p 23, Abbildung 3-19, top: Form \
fields do not have a visible label and also no describing title attribute. This \
applies e.g. to the serach field in the main menu as well as to all comboboxes with \
autocomplete functionality. </li>
<li>
Abbildung 3-19, bottom: The \
screen reader is not able to relate the labels to the input fields as the lables are \
in a separate table row above the input fiels and both are not linked. </li>
<li>
Abbildung 3-19, middle: The \
screen reader uses incorrect decsriptions for the checkboxes as they are not linked \
correctly with their labels. Additionally, due to the missing linking the active area \
for the checkboxes is too small for users with a movement disorder. </li>
</ul>
<p style="margin: 10px 0 0 0">This \
applies to most of the input fields of the application.</p>
<p style="margin: 10px 0 0 0">These \
findings are seen as an accessibility obstacle for blind users.</p>
<p style="margin: 10px 0 0 \
0">Recommendations (The most important ones):</p> <ul>
<li>
Each form field and its label \
should be linked in the HTML markup, e.g. <label for="search">Search \
for</label><input type="text" id="search" ... />. \
</li> <li>
Mandatory field indicators should \
be included in the label. </li>
<li>
Labels for input fields should be \
located before the corresponding field. </li>
<li>
Labels for checkboxes and radio \
buttons should be located after the corresponding element. </li>
<li>
Layout tables should not be used \
for laying out forms. If it is not possible to use an alternative layout, the form \
field ans its corresponding label should located be in the same row. </li>
</ul>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="email-content-main mobile-expand " \
style="padding: 0px; border-collapse: collapse; border-left: 1px solid #ccc; \
border-right: 1px solid #ccc; border-top: 0; border-bottom: 0; padding: 0 15px 0 \
16px; background-color: #fff"> <table id="actions-pattern" cellspacing="0" \
cellpadding="0" border="0" width="100%" style="border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt; font-family: Arial, sans-serif; \
font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; mso-text-raise: \
1px"> <tr>
<td id="actions-pattern-container" \
valign="middle" style="padding: 0px; border-collapse: collapse; padding: 10px 0 10px \
24px; vertical-align: middle; padding-left: 0">
<table align="left" \
style="border-collapse: collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt"> \
<tr> <td class="actions-pattern-action-icon-container" style="padding: 0px; \
border-collapse: collapse; font-family: Arial, sans-serif; font-size: 14px; \
line-height: 20px; mso-line-height-rule: exactly; mso-text-raise: 0px; \
vertical-align: middle"> <a \
href="https://jira.codehaus.org/browse/SONAR-6066#add-comment" target="_blank" \
title="{getText($action.text)}" style="color: #3b73af; text-decoration: none"> <img \
class="actions-pattern-action-icon-image" \
src="https://jira.codehaus.org/images/mail/comment-icon.png" alt="Add Comment" \
title="{Add Comment}-icon" height="16" width="16" border="0" style="vertical-align: \
middle" /> </a> </td>
<td \
class="actions-pattern-action-text-container" style="padding: 0px; border-collapse: \
collapse; font-family: Arial, sans-serif; font-size: 14px; line-height: 20px; \
mso-line-height-rule: exactly; mso-text-raise: 4px; padding-left: 5px"> <a \
href="https://jira.codehaus.org/browse/SONAR-6066#add-comment" target="_blank" \
title="Add Comment" style="color: #3b73af; text-decoration: none">Add Comment</a> \
</td> </tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
<!-- there needs to be content in the cell for it to render \
in some clients --> <tr>
<td class="email-content-rounded-bottom mobile-expand" \
style="padding: 0px; border-collapse: collapse; color: #fff; padding: 0 15px 0 16px; \
height: 5px; line-height: 5px; background-color: #fff; border-top: 0; border-left: \
1px solid #ccc; border-bottom: 1px solid #ccc; border-right: 1px solid #ccc; \
border-bottom-right-radius: 5px; border-bottom-left-radius: 5px; \
mso-line-height-rule: exactly">
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td class="contextual-area-pattern" style="padding: 0px; \
border-collapse: collapse; padding: 15px 20px 0 20px"> <table \
class="contextual-excerpt-pattern" cellspacing="0" cellpadding="0" border="0" \
width="100%" style="border-collapse: collapse; mso-table-lspace: 0pt; \
mso-table-rspace: 0pt; border-bottom: 1px solid #ccc"> <tr>
<td class="contextual-excerpt-pattern-text \
contextual-excerpt-pattern-text-container mobile-resize-text" valign="top" \
style="padding: 0px; border-collapse: collapse; font-family: Arial, sans-serif; \
font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; mso-text-raise: \
1px; padding: 4px 0 17px 0"> <div>
<table class="page-title-pattern" cellspacing="0" \
cellpadding="0" border="0" width="100%" style="border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt"> <tr>
<td class="page-title-pattern-first-line \
" style="padding: 0px; border-collapse: collapse; font-family: Arial, sans-serif; \
font-size: 14px; padding-top: 10px"> <a href="https://jira.codehaus.org/browse/SONAR" \
style="color: #3b73af; text-decoration: none">SonarQube</a> / <a \
href="https://jira.codehaus.org/browse/SONAR-6066" style="color: #3b73af; \
text-decoration: none"><img \
src="https://jira.codehaus.org/images/icons/issuetypes/improvement.png" height="16" \
width="16" border="0" align="absmiddle" alt="Improvement" style="vertical-align: \
text-bottom" /></a> <a href="https://jira.codehaus.org/browse/SONAR-6066" \
style="color: #3b73af; text-decoration: none">SONAR-6066</a> </td>
</tr>
<tr>
<td style="vertical-align: top;; padding: \
0px; border-collapse: collapse; padding-right: 5px; font-size: 20px; line-height: \
30px; mso-line-height-rule: exactly" class="page-title-pattern-header-container"> \
<span class="page-title-pattern-header" style="font-family: Arial, sans-serif; \
padding: 0; font-size: 20px; line-height: 30px; mso-text-raise: 2px; \
mso-line-height-rule: exactly; vertical-align: middle"> <a \
href="https://jira.codehaus.org/browse/SONAR-6066" style="color: #3b73af; \
text-decoration: none">Usability and accessibility issues</a> </span> </td>
</tr>
</table>
<div style="padding-top:10px;">
<table class="text-paragraph-pattern" \
cellspacing="0" cellpadding="0" border="0" width="100%" style="border-collapse: \
collapse; mso-table-lspace: 0pt; mso-table-rspace: 0pt; font-family: Arial, \
sans-serif; font-size: 14px; line-height: 20px; mso-line-height-rule: exactly; \
mso-text-raise: 2px"> <tr>
<td \
class="text-paragraph-pattern-container mobile-resize-text " style="padding: 0px; \
border-collapse: collapse; padding: 0 0 10px 0">
T-Systems delivered a usability \
report of SQ 4.5. File reports, in German, are attached. </td>
</tr>
</table>
</div>
</div>
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td id="footer-pattern" style="padding: 0px; border-collapse: \
collapse; padding: 12px 20px"> <table id="footer-pattern-container" cellspacing="0" \
cellpadding="0" border="0" style="border-collapse: collapse; mso-table-lspace: 0pt; \
mso-table-rspace: 0pt"> <tr>
<td id="footer-pattern-text" class="mobile-resize-text" \
width="100%" style="padding: 0px; border-collapse: collapse; color: #999; font-size: \
12px; line-height: 18px; font-family: Arial, sans-serif; mso-line-height-rule: \
exactly; mso-text-raise: 2px"> This message was sent by Atlassian JIRA <span \
id="footer-build-information">(v6.1.6#6162-<span \
title="7af547ce7c84dbb7c1e345a65437ed7b85efffa2" \
data-commit-id="7af547ce7c84dbb7c1e345a65437ed7b85efffa2}">sha1:7af547c</span>)</span>
</td>
<td id="footer-pattern-logo-desktop-container" \
valign="top" style="padding: 0px; border-collapse: collapse; padding-left: 20px; \
vertical-align: top">
<table style="border-collapse: collapse; \
mso-table-lspace: 0pt; mso-table-rspace: 0pt"> <tr>
<td id="footer-pattern-logo-desktop-padding" \
style="padding: 0px; border-collapse: collapse; padding-top: 3px"> <img \
id="footer-pattern-logo-desktop" \
src="https://jira.codehaus.org/images/mail/footer-desktop-logo.png" alt="Atlassian \
logo" title="Atlassian logo" width="169" height="36" class="image_fix" /> </td>
</tr>
</table>
</td>
</tr>
</table>
</td>
</tr>
</table>
</body>
</html>
<hr/>
<p>
To unsubscribe from this list please visit:
</p>
<p>
<a href="http://xircles.codehaus.org/manage_email">http://xircles.codehaus.org/manage_email</a>
</p>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic