5709a7858d5c197721be66d5218a79124abadb70
lrnassar
Tue Mar 17 08:46:31 2026 -0700
Adding alt text to images across static documentation pages, CGI headers, markdown docs, and Pandoc templates. Content images receive AI-generated descriptive alt text; decorative images (icons, spacers, toggles) receive alt="" per WCAG best practice. Also adds Image Descriptions section to the accessibility page, and fixes Pandoc Lua writers to output alt attributes. 67 files, covering help docs, news archive, ENCODE pages, portal pages, and session examples. refs #37254
diff --git src/hg/htdocs/goldenPath/help/bigLolly.html src/hg/htdocs/goldenPath/help/bigLolly.html
index 79e7873574c..4886877e3ba 100755
--- src/hg/htdocs/goldenPath/help/bigLolly.html
+++ src/hg/htdocs/goldenPath/help/bigLolly.html
@@ -10,31 +10,31 @@
The bigLolly format uses a standard bigBed file that is used to generate a lollipop graph where
the position of a lollipop circle corresponds to a genomic coordinate. By default, the score
is used to decide how high to draw the lollipop, but there are trackDb options to specify which
fields to use for the height and width of the lollipop, as well as to draw lines on the graph.
BigLolly trackDb options arguments are noStems, lollySizeField,
lollyMaxSize, lollyField, yAxisLabel, and
yAxisNumLabels. These options are also described in the
trackDb help doc.
This format is useful for displaying small genomic features such as sequence variants, as it provides two ways to characterize features and make them more visible -- stem height and radius -- in addition to color. The lollipop graph type can be used to annotate bases for variants, RNA editing, Selenocysteines, frameshifts, or any other reason.
-
+
The bigBed files used in bigLolly type are in an indexed binary format. The main advantage of this format is that only those portions of the file needed to display a particular region are transferred to the Genome Browser server. The bigLolly file remains on your local web-accessible server (http, https or ftp), not on the UCSC server, and only the portion needed for the currently displayed chromosomal position is locally cached as a "sparse file". If you do not have access to a web-accessible server and need hosting space for your bigLolly files, please see the Hosting section of the Track Hub Help documentation.
bedToBigBed utility to create a bigBed file from your sorted BED file, using
the bigLollyExample3.bed file and chrom.sizes files created above.
bedToBigBed -as=bigLollyExample3.as -type=bed9+1 bigLollyExample3.bed hg38.chrom.sizes bigLollyExample3.bb
track type=bigLolly name="bigLolly Example Three" description="A third bigLolly file" bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigLollyExample3.bb lollySizeField=lollySize visibility=full yAxisLabel.0="0 on 30,30,190 0" yAxisLabel.1="5 on 30,30,190 5" lollyMaxSize=10 lollyNoStems=on
-
+
Custom tracks can also be loaded via one URL line. This link loads the same bigLolly.bb track and sets additional display parameters from Example 1 in the URL:
http://genome.ucsc.edu/cgi-bin/hgTracks?ignoreCookie=1&db=hg38&position=chr21:17,002,145-17,159,243&hgct_customText=track%20type=bigLolly%20name=Example %20bigDataUrl=http://genome.ucsc.edu/goldenPath/help/examples/bigBedExample3.bb %20visibility=full
If you would like to share your bigLolly data track with a colleague, learn how to create a URL link to your data by looking at Example #6 on the custom track help page.