

\documentclass[11pt,twoside]{article}

% Do NOT use ANY packages other than asp2014. 
\usepackage{asp2014}

\aspSuppressVolSlug
\resetcounters


\bibliographystyle{asp2014}

% The ``markboth'' line sets up the running heads for the paper.
% 1 author: "Surname"
% 2 authors: "Surname1 and Surname2"
% 3 authors: "Surname1, Surname2, and Surname3"
% >3 authors: "Surname1 et al."
% Replace ``Short Title'' with the actual paper title, shortened if necessary.
% Use mixed case type for the shortened title
% Ensure shortened title does not cause an overfull hbox LaTeX error
% See ASPmanual2010.pdf 2.1.4  and ManuscriptInstructions.pdf for more details
\markboth{Schaaff, Mantelet, Boch, , and al}{Short Title}

\begin{document}


\title{Improving CDS Webpages Accessibility}

% Note the position of the comma between the author name and the 
% affiliation number.
% Authors surnames should come after first names or initials, eg John Smith, or J. Smith.
% Author names should be separated by commas.
% The final author should be preceded by "and".
% Affiliations should not be repeated across multiple \affil commands. If several
% authors share an affiliation this should be in a single \affil which can then
% be referenced for several author names. If only one affiliation, no footnotes are needed.
% See ManuscriptInstructions.pdf and ASP's manual2010.pdf 3.1.4 for more details
\author{Schaaff A.,$^1$ Mantelet G.,$^1$,boch T. $^1$, Feldis N.$^2$}
\affil{$^1$Observatoire astronomique de Strasbourg, Strasbourg, France; \email{andre.schaaff@astro.unistra.fr}}
\affil{$^2$Unistra, Strasbourg, France}

% This section is for ADS Processing.  There must be one line per author. paperauthor has 9 arguments.
\paperauthor{Andr\'e~Schaaff}{andre.schaaff@astro.unistra.fr}{0000-0002-8790-7048}{Observatoire astronomique de Strasbourg, Universit\'e de Strasbourg, CNRS, UMR 7550}{CDS}{Strasbourg}{Alsace}{67000}{Strasbourg}
\paperauthor{Grégory Mantelet}{Gregory.mantelet@astro.unistra.fr}{0000-0003-0105-5348}{Observatoire astronomique de Strasbourg, Universit\'e de Strasbourg, CNRS, UMR 7550}{CDS}{Strasbourg}{Alsace}{67000}{Strasbourg}
\paperauthor{Thomas Boch }{thomas.boch@astro.unistra.fr}{0000-0002-2335-4499}{Observatoire astronomique de Strasbourg, Universit\'e de Strasbourg, CNRS, UMR 7550}{CDS}{Strasbourg}{Alsace}{67000}{Strasbourg}
\paperauthor{Nathan Feldis}{nathan.feldis@etu.unistra.fr}{}{Observatoire astronomique de Strasbourg, Universit\'e de Strasbourg, CNRS, UMR 7550}{CDS}{Strasbourg}{Alsace}{67000}{Strasbourg}

% There should be one \aindex line (commented out) for each author. These are used to
% build up the author index for the Proceedings. The surname must come first, followed by
% initials. Note the use of ~ before each initial to control spacing.
% The \author entries (see above) have surname last. These \aindex entries have
% surname first.
% The Aindex.py command willl create them for you after you have constructed the \author
% The first entry should be the first author, for bold-facing the author index page-reference

%\aindex{FistAuthor1,~S.~A.}
%\aindex{Author2,~S.~B.}
%\aindex{Author3,~S.}


\section{abstract}
We are committed to making our web pages and astronomical data services accessible to all users, particularly people with disabilities. Rather than developing new accessibility tools, our focus has been on ensuring that our content can be fully processed by existing solutions, while adding new features where appropriate. Through awareness-raising and compliance testing against current accessibility standards, we identified and implemented targeted improvements across the CDS website and services. These changes, though incremental, significantly enhance accessibility for many users and support our broader goal of open, reusable scientific data.

\section{Web accessibility}
Web accessibility means designing websites, applications, and digital content so that everyone, including people with disabilities, can perceive, understand, navigate, and interact with them. It ensures equal access to information and functionality for users with Visual impairments (blindness, low vision, color blindness), Hearing impairments, Motor or mobility limitations or Cognitive or learning disabilities.


\articlefigure{image1.eps}{ex_fig1}{dedicated accessibility panel available in the services}

\articlefigure[width=0.8\linewidth]{image3.eps}{ex_fig3}{Galaxy candidates for 3D printing}

\articlefigure[width=0.8\linewidth]{image2.eps}{ex_fig2}{3D modelling of galaxies}





\section{Web Accessibility principles}

Web accessibility can be described through four main principles.
\begin{itemize}
    \item \textbf{Perceivable}: Information and user interface components must be presented in ways that users can perceive, for example by providing alternative text for images and captions for audio or video content.
    \item \textbf{Operable}: User interface components and navigation must be usable by all users, including through keyboard navigation, voice input, and assistive technologies.
    \item \textbf{Understandable}: Information and navigation should be easy to understand, using clear language and predictable interaction patterns.
    \item \textbf{Robust}: Content must be robust enough to be interpreted reliably across different browsers, devices, and assistive technologies.
\end{itemize}


\section{Why Accessibilty Matters}

Promoting digital inclusion is first and foremost an ethical and social responsibility. It is also a legal obligation, through compliance with accessibility standards such as the WCAG (Web Content Accessibility Guidelines) and regulatory frameworks including the European Accessibility Act (2025). Beyond these requirements, accessibility offers clear technical benefits by improving search engine optimization, enhancing user experience, and ensuring better mobile compatibility. Finally, from a scientific and institutional perspective, accessibility is essential to support open science and to ensure that public data and related services can be reused by all.

\section{Practical actions}

Accessibility should be validated using dedicated evaluation tools, such as those recommended by the W3C Web Accessibility Initiative. All images and icons must include meaningful alternative text, and sufficient color contrast should be ensured, with a minimum ratio of 4.5:1. Full keyboard navigation must be provided for all interactive elements.

The use of semantic HTML elements and appropriate ARIA labels is essential to ensure effective support for assistive technologies. In addition, captions and transcripts should be provided for all audio and video content, and websites should be tested using screen readers such as JAWS or VoiceOver.

\begin{itemize}
    \item Validate accessibility using dedicated tools (e.g. W3C Web Accessibility Initiative tools).
    \item Provide alternative text for images and icons.
    \item Ensure sufficient color contrast (minimum 4.5:1).
    \item Enable full keyboard access to all interactive elements.
    \item Use semantic HTML and appropriate ARIA labels.
    \item Provide captions and transcripts for audio and video content.
    \item Test websites with screen readers (e.g. JAWS, VoiceOver).
\end{itemize}


\section{Actions at at CDS}
\begin{itemize}
 \item Accessibility compliance testing using dedicated evaluation tools.
 \item Adoption of accessibility best practices and guidelines, including ARIA (Accessible Rich Internet Applications).
 \item Deployment of a dedicated accessibility library across all CDS web pages (see Figure~\ref{ex_fig1}).
 \item Exploratory developments in sonification and 3D modelling for 3D printing (see Figures~\ref{ex_fig2} and~\ref{ex_fig3}).
\end{itemize}



\section{Perspectives and Conclusion}
These efforts have been implemented across all web pages and extended with new features, such as sonification and 3D printing. Even incremental improvements can make a meaningful difference to the user experience.


% It is possible to reduce the size of a figure among other changes (see the instructions).  Here is an example:
% \articlefigure[width=.5\textwidth]{image1.eps}{ex_fig1_reduced}{Welcome to 1953 a little smaller.}

% There is a figure command allowing for three figures:
% \articlefigurethree{example.eps}{example.eps}{image1.eps}{ex_fig1_triple}{Now there are three of them.}

\bibliography{schaaff.bib}  % For BibTex

% if we have space left, we might add a conference photograph here. Leave commented for now.
% \bookpartphoto[width=1.0\textwidth]{foobar.eps}{FooBar Photo (Photo: Any Photographer)}

\end{document}
