Skip to content

LensesResearchLab/paperNIER-WebAccessibility-ase25

Repository files navigation

Autonomous Agents for Accessibility: Simulating Visual Impairments in Web Interfaces

Description

This repo contains the latex structure for the Autonomous Agents for Accessibility: Simulating Visual Impairments in Web Interfaces's NIER (New Ideas and Emerging Results) track.

Structure

  • preamble: contains all package and command definitions. Everything should be set by now, but if something needs defining this is the place to do it (look inside to see the structure)
  • bibfiles
    • local.bib: contains all local bib references i.e., references used for this paper specifically. Most references should be added here
    • bib folder: this folder contains many references used for multiple purposes, in particular the compsci.bib file contains many references on software engineering, programming languages, and adaptive systems. Check here if the reference exists before adding it to the local.bib file
  • Acronym.tex: contains all Acronyms used in the paper (look into the file for example of the definition). Acronyms are used with the \ac{ACRONYM} command
  • Pointers to objects in the text (e.g., images, tables, code, sections, code-line, ....) are referenced using the fancyref package using the command \fref{} respectively starting with (img:, tab:, lst:, sec:, ln:, ....)

Useful commands

  • \authorcomment[TYPE]{AUTHOR}{COMMENT} is used to leave annotation inlined with the text. Comments only appear in draft mode (the option in the documentclass in the main.tex file) and are invisible otherwise. TYPE can be comment, missing, idea, note, and author.
    • Frequent authors ( i.e., Mario, Camilo, Alejandro, Anamaria, Michael and Laura ) have custom annotation commands: \MARIO{}, \CAMILO{}, \ALEJO{}, \ANA{}, \MICHAEL{} and \LAURA{} that has 1 optional parameter (i.e., TYPE) and one mandatory parameter (i.e., COMMENT). If first parameter is not provided it, TYPE value "comment" would be assigned.
  • \ie \eg \cf are used respectively for the abbreviations i.e., e.g., cf.
  • listings are defined according to each specific language in the preamble file and generate their own environment (e.g., \ctxraits[....]{....} generates a contexts traits listing).

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 2

  •  
  •